◆ Asana

Manage permissions for users in sections

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 taskIn the 'Marketing Campaign Q3' project, give the design team editing rights for the 'Creative…+
In the 'Marketing Campaign Q3' project, give the design team editing rights for the 'Creative Assets' section, but only commenting rights for the 'Budget Approval' section.
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 the 'New Product Development' project kicks off, review the permissions for each…+
Before the 'New Product Development' project kicks off, review the permissions for each section. I need the engineering team to only edit their 'Technical Specs' section, but only view the 'Market Research' section. The product owner needs full control everywhere.
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 sales team just marked several 'leads' as 'closed' in the 'Sales Pipeline' project, but…+
The sales team just marked several 'leads' as 'closed' in the 'Sales Pipeline' project, but they're not supposed to be able to do that.
The sales team just marked several 'leads' as 'closed' in the 'Sales Pipeline' project, but they're not supposed to be able to do that – only the sales director can. I'm afraid this will mess up our reporting for Friday. How do I restrict their ability to change the status of leads in the 'Lead Qualification' section without preventing them from adding new leads or updating notes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find important sections of projects being modified by people who shouldn't have…+
I frequently find important sections of projects being modified by people who shouldn't have that level of access.
I frequently find important sections of projects being modified by people who shouldn't have that level of access, leading to rework and confusion. It feels like I'm always cleaning up after unintended changes. What habit should I change in how I set up section permissions to ensure that specific teams only have the right level of control over their designated areas?
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.