Team roles and access scopes explained

Compare Admin, Editor, and Viewer permissions across all resources, selected projects, and selected cards.

A role controls what a teammate can do. An access scope controls which workspace resources the teammate can see.

Roles

Can view, create, edit, and delete resources allowed by the access scope.

Can view, create, and edit resources allowed by the access scope. Editors cannot delete resources.

Can view allowed cards, projects, and analytics. Viewers cannot create, edit, duplicate, reset, or delete cards.

Applies the role across the owner's cards, projects, domains, and pixels.

Includes chosen projects and the cards inside them. Admins and Editors can create cards in this scope, but they cannot create new projects.

Includes only chosen cards and the project context needed to display them. New cards and projects cannot be created in this scope.

Need	Recommended setup
Manage the full shared workspace	Admin with All resources
Create and maintain cards for one department	Editor with Selected projects
Review one or more specific cards	Viewer with Selected cards

Domains and pixels require All resources.
Creating a project requires All resources.
Creating a card requires All resources or Selected projects.
Direct links, bulk actions, exports, selectors, and statistics follow the same role and scope checks.

Confirm the correct shared workspace is active, then ask the owner to check the member's scope and assignments.

The current role may not allow it. For example, Editors cannot delete and Viewers cannot change cards.

No. Personal and shared workspaces change the resources in view, not the signed-in identity.

Was this guide helpful?

Still have questions? Contact support and we'll help you out.