Project-level permissions

Project-level permissions allow you to configure permissions so that you can be precise about who has editing and viewing access to which project. We have also created the User role (alongside the Admin and Owner roles) which you must use in combination with Project-level permissions.

How does it work?

By clicking Share you can then configure the default permissions for the project using the dropdown. Here, you can set the project as private ("Has no access") or public ("Can view" or "Can edit").

“Has no access” means that projects are invisible to users who haven’t been expressly granted access (with the exception of Admins and Owners, who have access to all projects regardless of project-level permissions). Users will not be able to see nor access this project under any circumstance.

You are also able to assign specific users with their own permissions to a project. These user-level permissions will override the project's default permission setting – for instance, setting a project as "Has no access" by default, then inviting two specific team members with "Can edit" permissions, would mean that only the Project Owner and the two specific users will have access to this project.

We’ve also created a new role, the ‘User’ role. You must use the new User role in combination with project level permissions, since Admins and Owners are able to see all projects, irrespective of project level permissions.

Newly created projects are by default public.