Project roles and permissions are features that allow you to set specific access levels for project members. This enables precise control over who can view, comment on, edit, or manage different aspects of a project. There are four distinct roles available in a project, each with increasing levels of access and control:
Viewer: Can view all project content but cannot add comments, edit anything, or make any changes. This role is ideal for stakeholders who need to stay informed without actively participating in the project's modification.
Commenter: Can view the project and add comments to tasks and other elements. However, they cannot edit or modify any project content. This role is suitable for team members who need to provide feedback and discuss tasks without altering the project's structure.
Editor: Has comprehensive access to add, edit, and delete anything within the project. Editors can also invite and remove team members. This role is perfect for active team members directly involved in managing and executing project tasks.
Project Admin: Possesses full administrative control. Project admins can change project settings, modify all content, and even delete the project. They also have the unique ability to manage project roles for other team members. This role is typically assigned to project managers or leads who oversee the entire project lifecycle
The table below provides a comprehensive overview of the permissions associated with each project role:
Permission |
Viewer |
Commenter |
Editor |
Project Admin |
View tasks |
✅ |
✅ |
✅ |
✅ |
Comment on tasks |
❌ |
✅ |
✅ |
✅ |
Edit task details |
❌ |
❌ |
✅ |
✅ |
Assign tasks |
❌ |
❌ |
✅ |
✅ |
Set task status/section |
❌ |
❌ |
✅ |
✅ |
Manage custom fields |
❌ |
❌ |
✅ |
✅ |
Manage automation rules |
❌ |
❌ |
✅ |
✅ |
Edit project info |
❌ |
❌ |
✅ |
✅ |
Manage tabs |
❌ |
❌ |
✅ |
✅ |
Manage project members |
❌ |
❌ |
❌ |
✅ |
Archive/delete project |
❌ |
❌ |
❌ |
✅ |
View roles |
✅ |
✅ |
✅ |
✅ |