Project Members

A project member is a user with some level of access to that project.

Project members must also be a member of the account to which the project belongs. If their access to the account is removed, they will also be removed from any projects.

A user can be a member of an unlimited number of projects.

Permissions

To support accounts with a large number of users - particularly for businesses - it is possible to control resource access using a role-based permission model.

For resources that are part of a project, access is determined by the user's role within that project. If the user is not a member of the project, they have no access - neither read nor write - to the enclosed resources.

For resources that are not part of a project, the level of access is determined by the user's account role. This also controls what account-level actions they can perform.

Decision Tree

This flowchart depicts the logic used to determine a user's access level for a given resource.

Roles

Each project member has role, which determines which actions they can perform within that project. A user belonging to multiple projects may have a different role within each.

This role is unrelated to the user's account role, and only affects the level of access to resources within that project.

There are three roles available: Viewer, Editor, and Administrator.

Viewer

This role can be thought of as read-only access.

Users with it can view all project resources. However, they cannot create any new resources within the project, nor edit any existing resources.

This is the default role given to users who join an Open project of their own account.

Editor

This role can be thought of as read-write access.

Users with it can view and edit all existing resources within the project, and create new resources.

Editors cannot modify any project settings, or add or remove other users.

Administrator

This role is the same as Editor in terms of access to project resources, but it conveys additional permissions to modify the project itself.

Only users with this role can make changes to project settings, or alter its membership. When adding a new project, the user who creates it is automatically assigned the role.

Every project must have at least one Administrator. If the last member with this role leaves, another member is chosen at random to receive it. If there are no other members, the project is deleted (but resources contained within it are preserved).