Roles and permissions
Managing user access is essential for keeping your workspace and projects organized and secure. This section covers the basic roles available to all users and the advanced roles and permissions that offer additional flexibility and control.
Basic roles
Workspace roles
In the workspace, there are two primary roles that help manage the overall structure and user access:
- Owner: The Owner has full administrative control over the workspace. They can manage everything, including users, roles, and settings.
- Admin: Admins can manage users and roles within the workspace but cannot change overall workspace settings, remove Owners, change the role of an Owner, or invite users as Owners. They assist in managing user access and role assignments.
For a step-by-step guide on how to invite user to the workspace, please refer to the How to invite member section.
Advanced roles and permissions (Teams plan only)
Additional workspace role
The advanced roles introduce an additional workspace role, Member. Members have basic access to participate in workspace activities but cannot manage users or roles. This role allows more team members to contribute without administrative privileges.
Project roles
Project roles are custom roles created within the workspace that can be assigned to different projects. These roles consist of specific permissions that define what actions users can perform within each project. Custom roles offer precise control over user actions and can be reused across multiple projects. This flexibility is essential for tailoring permissions to meet the specific needs of each project.
For detailed instructions on creating custom roles, please refer to our How to create role tutorial, which includes step-by-step guidance and screenshots.
Permissions in projects
Permissions in projects control what actions users can perform. These permissions ensure that each team member has the appropriate access level to perform their tasks efficiently.
| Permission | Overview |
|---|---|
| Can view project content | Allows users to view project content and is essential for all users who should have access to the project. Without this permission, users cannot see the project data even if they have other permissions. For example, if a user has the “Can create item” permission but does not have the “Can view project content” permission, they cannot view the list of items. |
| Can export items | Grants users the ability to export project data. |
| Can setup navigation | Allows users to configure project navigation. |
| Can view changes in instance sync | Allows users to view changes available for syncing between project instances. |
| Can move changes between instances | Permits users to transfer changes between different project instances, essential for roles involved in the deployment process. |
| Can create item | Allows users to create new items within the project. |
| Can create template | Grants users the ability to create templates for reuse, useful for standardizing processes. |