Roles and Permissions

RBAC Overview

Tracelane uses a role-based access model at two levels:

1. Workspace roles – define what a user can do across the entire workspace.
2. Project roles – define what a user can do within a specific project.

Workspace role vs project role

Workspace roles and project roles are independent of each other, with two exceptions: If a user is removed from a workspace, the user automatically loses access to all projects within that workspace.

Workspace Roles

Access in Tracelane starts at the workspace level. Each workspace member has one of three roles: Owner, Member or Reader.

• Owner: Manages the workspace. Owners can invite new members, create projects, and configure workspace-wide settings.
• Member: Has no global permissions at the workspace level. Their abilities depend on the roles they are assigned within individual projects.
• Reader: Can view all data but not edit/comment on it. Readers are free (for more information check the billing page)

Workspace Permissions Overview

Permission	Reader	Member	Owner
Read everything inside projects	✓	✓	✓
Edit everything inside projects		✓	✓
Use AI features		✓	✓
Create new projects			✓
Invite new colleagues to the workspace			✓
Manage billing details and workspace settings			✓
See projects where you are not explicitly a member			✓

Project Roles

Project membership is managed independently for each project. A project owner can add or remove workspace members from their project.

Available roles within a project:

• Guest
  Can view project modules and content, but cannot make changes.
• User
  Can edit modules, create links between elements, and fully work inside the project.
• Owner
  Has full control, including managing project members and deleting the project.

Project Permissions Overview

Permission	Guest	User	Owner
Read all modules and content	✓	✓	✓
Edit all modules and content		✓	✓
Create links between elements		✓	✓
Use AI features for requirements analysis		✓	✓
Add or remove project members			✓
Delete the project			✓