Roles and permissions
Give members exactly the rights they need with custom roles, like Project lead or Guest editor.
Every person in a workspace is an Admin or a Member. Admins can do everything. Members can do the everyday work, and custom roles let admins widen or narrow what a member can do.
Built-in roles
| Role | What they can do |
|---|---|
| Admin | Everything, including billing, integrations, workspace settings, making others admins and editing roles. |
| Member | Work on tasks and projects they can see, and by default create projects, manage custom fields, automations and team dashboards. |
Create a custom role (admins)
- 1Open Settings → Roles & permissions and click New role.
- 2Name it, for example Project lead.
- 3Tick the permissions it should have. Each one has a short explanation.
- 4Click Create role.
Give someone a role
In the Who has which role list on the same card, pick a role next to the person. A custom role replaces the default member permissions, so tick everything that person should still be able to do. Choosing Member puts them back on the defaults.
- Admins always have every permission. To limit an admin, first make them a member under Settings → Members.
- Deleting a role moves its people back to Member.
- Members whose role includes Change roles and remove people can also assign roles, but only roles whose permissions they have themselves, and never to admins or themselves.
What a role can't grant
Billing, deleting the workspace, connecting integrations (Slack, GitHub, GitLab, Microsoft), renaming the workspace, making someone an admin and editing roles always stay with admins.
People with Invite people can only invite members, not admins.
Related articles
Still stuck? Tell us what you were trying to do and we'll help.
Contact support