Roles
Roles define what people can see, configure, and change in a workspace or team.
Workspace roles
| Role | Scope |
|---|---|
| Owner | Manages Billing, workspace settings, integrations, members, apps, API Keys, and taxonomy. |
| Admin | Helps manage workspace settings, integrations, members, apps, API Keys, and taxonomy. Can start the first upgrade from Billing when the workspace is not yet on a paid account. |
| Member | Participates in workspace work, teams, initiatives, tasks, recaps, and standups. |
A workspace can have multiple owners.
Limit owner and admin access to people who need workspace-wide administration.
Team roles
| Role | Scope |
|---|---|
| Admin | Configures team standups, integrations, team channel, and team membership while also participating in team work. |
| Member | Participates in team work, standups, planning boards, recaps, and insights. |
| Observer | Views team context without contributing standup updates or team work. |
| Coordinator | Manages team setup without participating in team work. |
Team roles only apply inside that team. They do not grant access to other teams by themselves.
External permissions
Connected apps such as GitHub, GitLab, Slack, Linear, Jira, and Google Calendar keep their own user-level access rules. Permissions covers the full access model.