Custom Roles
Build reusable project roles from a base plus per-module access, defined once for the whole organization.
A custom role is a reusable project role you define once at the organization level. It is then available on every project in the organization. Use custom roles when the three built-in roles do not fit, for example when a stakeholder should edit one module but only view the rest.
Who can create them
Custom roles are managed by organization Admins only. The Manage Roles page and its Custom Roles table are restricted to Admin and Super Admin. Members cannot see or reach it.
How a custom role is built
A custom role starts from a base and layers module access on top:
- Base No Access starts from zero. You grant access module by module.
- Base Viewer starts from view-and-comment everywhere. You raise specific modules to Editor.
For each module you set a level of Viewer or Editor. Access only ever adds, so to give less on a module, choose a lower base rather than trying to remove a single permission.
Open Manage Roles
Go to Settings → Organization → Manage Roles.
Add a custom role
In the Custom Roles table, create a role and give it a unique name.
Choose a base
Pick No Access or Viewer as the starting point.
Grant module access
Set Viewer or Editor on the modules the role should reach.
Save and assign
Save the role, then assign it to members on any project.
Rules to know
- Names are unique. A name must be unique in the organization. Matching is case-insensitive and trims leading and trailing spaces, so "Tech Lead" and " tech lead " are treated as the same name. A custom role also cannot reuse a built-in role name (Viewer, Editor, or Owner).
- No member management. A custom role can never grant member management, whatever its base or grants. That stays with Owners and organization Admins.
- Edits apply immediately. Editing a role that is already assigned takes effect right away. 8090 Software Factory shows a confirmation dialog naming how many members and projects are affected before it applies.
What deleting a custom role does
Deletion changes the people who hold the role, atomically with the delete. If the role's base is Viewer, everyone assigned to it drops to the Viewer project role. If the base is No Access, everyone assigned to it is removed from the affected projects.
A View seat is capped at the Viewer project role, so a custom role assigned to someone on a View seat cannot raise any module above Viewer, whatever the role's grants.
Examples
| Role | Base | Grants | Good for |
|---|---|---|---|
| QA Triager | No Access | Work Orders: Editor, Feedback: Editor | Someone who files and manages work orders and feedback but should not touch Requirements or Blueprints. |
| Docs Editor | Viewer | Knowledge Base: Editor, Requirements: Editor | Someone who sees and comments on everything and edits documentation and requirements. |
| Automations Author | Viewer | Automations: Editor | Someone who views the whole project and builds and manages their own automations, nothing more. |
Next, see the Permissions reference.