◆ Asana

Manage role-based access control

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGive Sarah from marketing and David from legal view-only access to the 'Q4 Product Launch'…+
Give Sarah from marketing and David from legal view-only access to the 'Q4 Product Launch' project. Everyone else on the project team needs full editing rights.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize the 'Client Onboarding' project, make sure only the client success team can…+
Before I finalize the 'Client Onboarding' project, make sure only the client success team can edit tasks, and everyone else can only comment. I want to prevent accidental changes but still allow feedback.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new intern just accidentally deleted a critical task from the 'Website Redesign' project,…+
The new intern just accidentally deleted a critical task from the 'Website Redesign' project.
The new intern just accidentally deleted a critical task from the 'Website Redesign' project, and I'm terrified they'll do it again. I gave them full access like everyone else. How do I let them contribute without risking the whole project, especially with the Friday deadline looming? What's the best way to restrict their access to just what they need to do without making them feel untrusted?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having to fix things after new team members accidentally change critical project…+
I keep having to fix things after new team members accidentally change critical project details.
I keep having to fix things after new team members accidentally change critical project details, especially in the first week. It's eating up my time and making me look disorganized. What habit should I change in how I set up new projects or onboard people to prevent these early mistakes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Asana's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.