1. Overview
Project roles control what a member can see and do within a specific project. Project roles are independent of account-level roles and are assigned separately — any workspace member can be a project Owner regardless of their account role (see Section 5).
2. Roles at a Glance
Permission | Owner | Editor | Viewer |
View project content | ✓ | ✓ | ✓ |
Edit project content | ✓ | ✓ | — |
Export, duplicate, or comment | ✓ | ✓ | — |
Share the project (invite as Editor or Viewer) | ✓ | ✓ | — |
Remove members (below own level) | ✓ | ✓ | — |
Delete project content | ✓ | — | — |
Delete the project | ✓ | — | — |
Transfer project ownership | ✓ | — | — |
Content within a project — chats, matrices, notes, and other items — inherits the project's access setting automatically; there is no separate sharing mechanism per document.
3. Role Descriptions
3.1 Owner
The project Owner holds full control over the project: read, write, and delete access to content, management of all members at any level, and the ability to transfer ownership to another workspace member. Each project has exactly one Owner.
Typical assignment: the team member responsible for the project — typically its creator or the party accountable for delivery.
3.2 Editor
Editors can view and modify project content, and export, duplicate, or comment on it. An Editor can share the project by inviting new members as Editor or Viewer, and can remove members below their own level. An Editor cannot promote a member to Owner, delete the project, or transfer ownership.
Typical assignment: active collaborators who contribute regularly and need to bring in colleagues without routing every invitation through the Owner.
3.3 Viewer
Viewers hold read-only access: content can be followed and read, but not edited, exported, duplicated, or commented on, and a Viewer cannot invite others.
Typical assignment: stakeholders, clients, or colleagues requiring visibility without editing rights.
4. Sharing Rules
Both Owner and Editor can share a project, subject to one constraint: a member cannot grant more access than they hold themselves. An Editor can invite a new member as Editor or Viewer, but not as Owner. Only the project Owner can assign ownership or promote a member above Editor level.
When sharing, the inviter enters the recipient's email address and selects Editor or Viewer at the point of invitation. Escalation of privilege beyond this always requires deliberate action by the Owner.
5. Relationship to Account Roles
Project roles are independent of account roles. A workspace Member can be the Owner of a project, while an account Admin may hold only Viewer access on that same project unless added at a higher level. Account Owners and Admins can view and manage all projects in the workspace regardless of their assigned project role (see Account Roles: Owner, Admin, and Member).
6. Sharing a Project
Open the project and go to Members.
Click Share and enter the recipient's email address.
Select a role: Editor or Viewer (an Owner sharing the project can also select Owner).
Click Send.
7. Changing a Project Member's Role
Open the project and go to Members.
Locate the member whose role is to be changed.
Click the role dropdown next to their name and select the new role.
An Owner can change any member's role. An Editor can change roles only for members below their own level.
8. Frequently Asked Questions
Question | Answer |
Can a project have more than one Owner? | No. Each project has a single Owner. Use Transfer Ownership to hand over control. |
Can a Viewer download or duplicate content? | No. Exporting, duplicating, and commenting require Editor access or higher. |
Can an Editor remove another Editor? | No. An Editor can remove only members below their own level (Viewers). Removing another Editor or the Owner requires Owner rights. |
What happens if the project Owner leaves the workspace? | Ownership must be transferred before the Owner's account is removed. Account Admins can reassign ownership if needed; contact support if access is blocked. |