◆ Asana

Set permissions for teams

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 taskSet the 'Executive Leadership Team' team to private, so only invited members can see its…+
Set the 'Executive Leadership Team' team to private, so only invited members can see its projects and conversations. Add Sarah as an admin to this team.
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 acceptOur 'External Partners' team currently allows all members to create new projects and invite…+
Our 'External Partners' team currently allows all members to create new projects and invite anyone, which has led to some disorganized work. Can we set a rule for this team that only team admins can create new projects and invite members, while regular members can only create tasks within existing projects?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new marketing manager just joined, and she was automatically added to the 'All Company' team…+
A new marketing manager just joined, and she was automatically added to the 'All Company' team with full admin rights.
A new marketing manager just joined, and she was automatically added to the 'All Company' team with full admin rights. This means she can see and potentially change projects across departments, which is far too much access for her role. I'm afraid she might accidentally disrupt something or see confidential HR projects. I can't tell my boss I set up the default wrong. What's the immediate action to scale back her team permissions without raising a red flag?
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 new hires or role changes result in incorrect team-level access, creating…+
I frequently find new hires or role changes result in incorrect team-level access, creating security risks.
I frequently find new hires or role changes result in incorrect team-level access, creating security risks or exposing sensitive information. This means I'm constantly reacting to potential issues instead of preventing them. How can I establish a better habit or automated process for managing team permissions, so that access levels are appropriate from day one for any new member or role change, without my constant manual intervention?
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.