Set project permissions

Set project permissions in Asana — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
The new product project needs design and marketing editors to restrict who can move tasks or change…
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.

Improve — make it easier to accept

+
Before I change permissions, make it clear who needs edit rights and why: list actions that must…
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.

Decide — diagnose the stuck moment

+
Three milestone dates moved forward by a vendor and I don’t know if they had delegated edit rights…

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?

Become — change the pattern

+
We keep getting unauthorized edits from contractors because permissions were granted too broadly…

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.

Next to this one

Other work management work people do in Asana.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.