◆ Asana

Set project permissions

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 taskThe new product project needs design and marketing editors to restrict who can move tasks or…+
The new product project needs design and marketing editors to restrict who can move tasks or change dates. Set project permissions so only project leads Priya and Jamal can change task deadlines, allow contributors to comment and update status but not reassign, and audit current access to revoke any former contractors' 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 change permissions, make it clear who needs edit rights and why: list actions that…+
Before I change permissions, make it clear who needs edit rights and why: list actions that must remain restricted, identify users who currently have unnecessary edit privileges, propose a permissions matrix that balances speed and control, and call out any users who will need an exception for the launch weekend.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThree milestone dates moved forward by a vendor and I don’t know if they had delegated edit…+
I just saw a vendor moved three deadlines earlier and no one approved it.
Three milestone dates moved forward by a vendor and I don’t know if they had delegated edit rights or exploited a permission gap. Which two checks will tell me whether permissions were misassigned and what immediate permission change will stop further unauthorized edits without blocking the essential contributors?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep getting unauthorized edits from contractors because permissions were granted too…+
We repeatedly have unauthorized deadline changes from contractors.
We keep getting unauthorized edits from contractors because permissions were granted too broadly and never reviewed. Which recurring habit will most reduce this risk: quarterly permission audits, stricter onboarding checklist, or role-based templates? Recommend the single habit to adopt, and outline a one-page audit routine to run before every major release.
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.