Roles

Use roles to 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.
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. These roles can manage settings across the workspace, so they should not be used as convenience roles for normal team participation.

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. Provider permissions continue to control what each user can access there.

For the full access model, see Permissions.