◆ Asana

Set access levels for team members

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 taskFor the 'Q4 Sales Targets' project, grant read-only access to all tasks for external…+
For the 'Q4 Sales Targets' project, grant read-only access to all tasks for external consultants, but ensure they cannot see the 'Compensation Details' section of any task.
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 onboard the new interns next week, set up their access. They need to see all tasks in…+
Before I onboard the new interns next week, set up their access. They need to see all tasks in the 'Marketing Campaigns' project, but only be able to comment on tasks, not edit or mark them complete. For the 'Team Resources' project, they should have full editing rights.
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 product launch involves external design agencies and manufacturing partners. I need to…+
Our new product launch project involves external vendors, and I'm unsure how much visibility to give them without exposing internal strategy.
The new product launch involves external design agencies and manufacturing partners. I need to give them access to relevant tasks, but I'm really nervous about them seeing our internal strategic discussions or upcoming feature roadmap. What's the best approach to set up their access so they have what they need to do their work, but nothing more?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm frequently answering questions about who can see what in our various project spaces,…+
I constantly get questions about who can see what in our project spaces.
I'm frequently answering questions about who can see what in our various project spaces, especially when new team members join or external partners are brought in. It feels like I'm always explaining the same access rules. What habit should I change to make access permissions clearer and more intuitive for everyone involved?
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.