Permissions and Access Troubleshooting
1 min read
Use this guide when an action is missing, a page is read-only, or access does not look the way you expect.
A Button or Action Is Missing
Section titled “A Button or Action Is Missing”Missing actions usually mean your current workspace or project role does not include that permission.
Check:
- You are in the correct workspace.
- You are in the correct project.
- Your workspace role allows workspace-level actions.
- Your project role allows project-level actions.
- The item is not in a read-only state.
Ask a workspace or project administrator to review your role if needed.
A Page Is Read-Only
Section titled “A Page Is Read-Only”A page may be read-only because:
- Your role allows viewing but not editing.
- The item is completed, archived, deprecated, or otherwise protected.
- You are viewing workspace-level shared configuration from a project page.
- The role is a built-in system role.
Project Access Looks Wrong
Section titled “Project Access Looks Wrong”Project access can come from:
- Direct project role assignment.
- Group-based project access.
- Workspace-level access that allows visibility into workspace settings.
If direct access is removed but the user still sees a project, check group membership and group project assignments.
User Cannot Access a Workspace
Section titled “User Cannot Access a Workspace”Confirm that:
- The user has accepted the workspace invitation.
- The user was not removed from the workspace.
- Their account email matches the invited email.
- Their workspace membership is active.
Access Tokens Have Different Rules
Section titled “Access Tokens Have Different Rules”Access tokens use workspace or project scopes and role pickers. They are not the same as a person signing in.
If automation fails, check token status, expiry, scope, and assigned roles.