Skip to content

Project Roles

The Project Roles page lets you create and manage the role labels that are assigned to project participants. Roles are tenant-wide and shared across all projects. Each participant on a project is assigned exactly one role from this list. Roles wire directly into the project authorization model: members receive scoped permissions based on the role they hold on each project.

Open Projects from the sidebar and navigate to Settings → Project Roles. Visibility requires at least Read-level access to the projects.project_roles permission.

Project Roles list

  • View all project roles defined for the tenant.
  • Search roles by name or key.
  • Filter to show only system roles or only custom roles.
  • Create new roles.
  • Edit existing role names, keys, and descriptions.
  • Reorder roles by dragging.
  • Delete roles that are not in use.
  • Initialize the list with a set of suggested roles in one step.
FieldRequiredDescriptionValidation
NameYesDisplay name shown in dropdowns and participant listsMax 128 characters
KeyYesUnique machine-readable identifier (slug format recommended)Max 64 characters; must be unique within the tenant
DescriptionNoShort explanation of the role’s purpose

When the tenant has no roles yet, the page shows a No roles yet empty state with a Use suggested roles button in the toolbar:

Project Roles empty state

Click Use suggested roles to open the Initialize project roles dialog. It lists six suggested role templates with Select all missing roles preselected. Adjust the selection if needed, then click Add selected roles to create them in one step.

Initialize project roles dialog

RoleDescription
OwnerAccountable owner for project direction and outcomes
Project ManagerCoordinates planning, scope, and delivery follow-up
DeveloperContributes implementation work
QA ReviewerReviews quality and validates acceptance criteria
ViewerReads project progress without direct delivery ownership
StakeholderBusiness stakeholder receiving progress updates

Already-existing roles are shown disabled with an Exists badge so they cannot be re-added.

Roles are displayed in sort order. To change the order, drag a role card by its grip handle and drop it in the new position. The order is saved automatically to the server. If the save fails, the order reverts to the previous state.

Reorder operations require Write-level permission. On desktop, role rows include a drag handle column on the left. On mobile, each role card shows its own drag handle.

Roles marked with the System badge are managed by the platform. System roles cannot be deleted, but their names and descriptions can be edited.

FilterDescription
SearchMatches role name or key (case-insensitive)
TypeShow All types, System only, or Custom only

Filters apply client-side to the loaded role list. Active filters are shown as removable chips above the results.

ActionRequired PermissionDescription
Create roleWrite (project_roles)Opens the Create Role dialog
Edit roleWrite (project_roles)Opens the Edit Role dialog
Delete roleAdmin (project_roles)Deletes the role after confirmation
Reorder rolesWrite (project_roles)Drag-and-drop reorder; saved automatically
Initialize rolesWrite (project_roles)Seeds selected suggested roles

Superusers bypass permission checks and have full access.

RuleBehavior
Name requiredSave disabled while Name is empty
Key requiredSave disabled while Key is empty
Key must be uniqueSaving with a duplicate key returns an error
Role in useDeleting a role that is assigned to one or more participants is blocked with the message “Project role is in use by active participants.” Remove or reassign all participants using this role before deleting it.
Access levelWhat the user can do
ReadView and filter roles
WriteCreate, edit, and reorder roles; initialize suggested roles
AdminAll Write actions plus delete roles

Users without Read access on project_roles see an access-denied message and cannot view the list.

Relationship to Project Participants and Authorization

Section titled “Relationship to Project Participants and Authorization”

Roles created here appear in the Role dropdown on the Project Participants panel. Changing a role’s name is reflected immediately on all participants already assigned that role. Roles also feed the project authorization model: when a tenant user is added as a participant with a given role, the system applies the permissions scoped to that role for the specific project.