Hello Asana community,
We’re launching a new “Viewer” access level for projects, and with that, we wanted to share an upcoming update to project permissions. But before diving in, let me start by giving you some context.
Currently, members gain access to a project in one of two ways – via direct membership to the project or via direct membership they have to either a team or the organization. Sometimes, this results in members getting conflicting permissions to a specific project; for example, they may get “Commenter” permissions through their project membership, while they’re “Editor” via their team membership.
Currently, Asana always gives members the lowest level of access they are entitled to. With this update, members will automatically granted the highest level of access shared with them. For example, project member is given ‘Commenter’ access individually, and as part of a ‘Design’ team, they have ‘Editor’ access (see image below for visual representation)
Q&A:
Why are you implementing this change?
Goals and portfolios are already operating under this model; we’re bringing it to projects to ensure access control is clear, secure, and consistent across all surfaces.
What actions will super admins and project admins need to take prior to viewer access level rollout?
Super admins are required to review their projects for any conflicting permissions and decide whether to elevate each member to their highest access level or leave the decision up to project admins who will have the ability to either upgrade or downgrade on a project level.
- Eg: if a user has ‘Commenter’ access in one role and ‘Editor’ access in another, project admins must decide whether to upgrade them to ‘Editor’ or align everyone in the project to ‘Commenter’ access.
Super admins and project admins will have 30 days to make a selection, after which Asana will upgrade users to their level of access if they have multiple access levels (as a result of being added directly to a project and indirectly, such as through a team). Both super admins and project admins will receive a notification by email and in-product informing them when they can facilitate this change.
How will I know which of my projects need to be updated?
Project admins will have a list of projects with mixed permissions and will be able to update their preferences from there:
How can I update permissions of projects impacted?
Project admins will be able to make permission changes by clicking on the banner on the specific project or sharing modal.
What happens if a decision is not made by the end of the 30-day period?
Asana will automatically upgrade all members to their highest level of access in projects with unresolved conflicting permissions.
When can I expect to see these changes happening?
Organizations who do not have conflicting permissions for a same user on a project will gradually see this new update rolling out to their account mid-February. Organisations with outstanding conflicting project permissions, will be gradually migrated in April.
To learn more, we recommend checking this guide article, but don’t hesitate to let us know in the comments if you have any questions or feedback!
Test team” an editor of this project. This doesn’t mean your project members are members of the team where your project lives
