This article details the project privacy and permissions settings that can be applied to projects in Asana, to determine which users can access or take actions within a project.
Explore project permissions for free. Start a free Asana trial today.
Access to a project in Asana is contextual, and there are a variety of situations that affect who can access a project and its tasks. If someone has access to a project, then they have access to all tasks and messages within it.
See the table below for a quick overview of how different project privacy settings determine which users can access a project.
|
Project privacy setting |
Project accessible to |
| Private to members | Members of the project, including people or teams |
| Shared with organization (for example, Shared with Alpha, Inc.) |
Members of the project, members of the team, and members of the organization |
Note that these project privacy settings are separate from read-only links. Because free users can only share with a single team, they will see a third "Shared with team" privacy setting option.
Private to members restricts access to the project to the people or teams who are explicitly added to the project. When a project is private to project members, non-members must request access to the project. Non-members will not see private to members projects in their search results.
Users have the option to share a project with a team when creating it, but that project will become Private to members with the team added as a member after creation.
Shared with team grants access to the project to members of the team in which the project resides. With this privacy setting, all direct members and team members can access the project.
For public teams, any member or guest in the organization can choose to join the public team and thereby access the project. Check the permissions of the team the project lives in to verify whether other users might access a project by joining a public team.
Shared with organization allows a project to be shared with those in the Asana organization, regardless of project or team membership.
Those who have access to a Shared with organization project include:
The shared with organization privacy setting is available in paid organizations. It is not available with a team or division subscription.
For detailed information on sharing projects and portfolios with entire teams, visit our dedicated Team sharing article.
Project members can be given individual permissions regardless of the project's task collaborator setting.
For more detailed information, visit our individual project permissions article.
Project admins can control who can modify specific custom field values in a project. This ensures data integrity for workflows that require it.
For more detailed information, visit our restricted custom field values article.
Note
Still unsure about project permissions? Ask the Community.