Skip to content

Roles and Permissions

SetGet uses a layered role system to control what each person can see and do. Permissions are enforced at two levels: workspace roles govern access to workspace-wide settings and capabilities, while project roles control what a member can do within a specific project. This page documents every role and provides a comprehensive permissions matrix.

Workspace roles

Every workspace member is assigned exactly one workspace role. The role determines their baseline permissions across the entire workspace.

Admin

Admins have unrestricted access to the workspace. They can manage settings, billing, members, integrations, and all projects. Every workspace must have at least one Admin.

Typical Admin responsibilities:

  • Configuring workspace settings and branding
  • Managing billing and subscription
  • Inviting and removing members
  • Setting up integrations and webhooks
  • Creating and archiving projects

Member

Members are the standard role for day-to-day contributors. They can create projects, manage work items, participate in cycles and modules, and collaborate on pages. They cannot access workspace-level settings, billing, or member management.

Guest

Guests have restricted, read-only access. They can only view projects they are explicitly added to and cannot create new projects or modify workspace settings. The Guest role is designed for external stakeholders, clients, or contractors who need visibility without edit capability.

TIP

Start by inviting everyone as Members. Promote to Admin only the people who need to manage workspace settings and billing. Use Guest for external collaborators.

Project roles

Within each project, members can have an additional project-level role that overrides or supplements their workspace role for that project:

Project RoleDescription
AdminFull control over the project, including settings, member management, and deletion
MemberCan create and edit work items, cycles, modules, pages, and views within the project
ViewerRead-only access to the project contents

A workspace Member who is a project Admin can manage that specific project's settings even though they cannot access workspace-level settings.

A workspace Guest can be added to specific projects as a Viewer to see project contents.

Permissions matrix — Workspace level

The following table covers workspace-wide actions and which roles can perform them:

ActionAdminMemberGuest
View workspace homepageYesYesYes
Edit workspace name and logoYesNoNo
Edit workspace settingsYesNoNo
Delete workspaceYesNoNo
Invite membersYesNoNo
Remove membersYesNoNo
Change member rolesYesNoNo
View member listYesYesLimited
Manage billing and subscriptionYesNoNo
Create projectsYesYesNo
View all projectsYesYesNo
Manage integrationsYesNoNo
Configure webhooksYesNoNo
Manage API tokensYesOwn onlyNo
Access workspace analyticsYesYesNo
Access archivesYesYesNo
Create teamspacesYesYesNo
Manage teamspacesYesOwn onlyNo
Create dashboardsYesYesNo
Import dataYesNoNo
Export dataYesYesNo

Permissions matrix — Project level

The following table covers project-scoped actions. Permissions depend on the member's project role:

ActionProject AdminProject MemberProject Viewer
View projectYesYesYes
Edit project settingsYesNoNo
Delete projectYesNoNo
Add project membersYesNoNo
Remove project membersYesNoNo
Create work itemsYesYesNo
Edit work itemsYesYesNo
Delete work itemsYesYes (own)No
Change work item statusYesYesNo
Assign work itemsYesYesNo
Add commentsYesYesNo
Delete commentsYesOwn onlyNo
Create cyclesYesYesNo
Edit cyclesYesYesNo
Delete cyclesYesNoNo
Create modulesYesYesNo
Edit modulesYesYesNo
Delete modulesYesNoNo
Create pagesYesYesNo
Edit pagesYesYesNo
Delete pagesYesOwn onlyNo
Create viewsYesYesYes
Edit viewsYesYesOwn only
Delete viewsYesOwn onlyOwn only
Manage labelsYesYesNo
Manage estimatesYesNoNo
Manage automationsYesNoNo
View activity logYesYesYes

Permissions matrix — Cycles and modules

ActionProject AdminProject MemberProject Viewer
Create cycleYesYesNo
Edit cycle dates and nameYesYesNo
Add work items to cycleYesYesNo
Remove work items from cycleYesYesNo
Delete cycleYesNoNo
Transfer incomplete itemsYesYesNo
Create moduleYesYesNo
Edit moduleYesYesNo
Link work items to moduleYesYesNo
Delete moduleYesNoNo

Permissions matrix — Pages

ActionProject AdminProject MemberProject Viewer
Create pageYesYesNo
Edit any pageYesYesNo
Delete own pageYesYesNo
Delete others' pagesYesNoNo
Lock page (prevent edits)YesNoNo
Archive pageYesYes (own)No

How roles interact

When a member has both a workspace role and a project role, the effective permission is the higher of the two. For example:

  • A workspace Admin always has full access to every project, regardless of their project role.
  • A workspace Member with a project Admin role can manage that project's settings but still cannot access workspace billing.
  • A workspace Guest with a project Viewer role can view that project but nothing else.

WARNING

Workspace Admins automatically have Admin-level access to all projects. You cannot restrict a workspace Admin within a specific project.

Changing roles

  • Workspace roles are changed in Settings > Members. See Workspace Members.
  • Project roles are changed within the project's Settings > Members page.