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
Every organization member can open Settings → Organization → Manage Roles and read the role definitions. Only organization Admins can create, edit, and delete custom roles.
How a custom role is built
A custom role starts from a base and layers module access on top:
- No Access starts from zero. You grant access module by module.
- Viewer starts from view-and-comment everywhere. You raise specific modules to Editor.
For each module you set a level of No Access, Viewer, or Editor. The modules are Automations, Knowledge Base, Requirements, Blueprints, Skills, Work Orders, Feedback, and Codebase Connection. 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
Select Create Custom Role, then enter a unique Role Name and, optionally, a description.
Choose a base
Under Base Project Access, pick No Access or Viewer as the starting point.
Grant module access
Under Module Access, set Viewer or Editor on the modules the role should reach. If you leave Skills at No Access, the form warns that this may reduce agent and automation effectiveness.
Save and assign
Save the role, then assign it to members from any project's Settings → Members & Roles.
Rules to know
- Names are unique. A name can be up to 100 characters and must be unique in the organization. Capitalization and spaces at the start or end don't count, so "Tech Lead" and "tech lead" are the same name. A custom role also can't use 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. Confirm Definition Changes shows how many members and projects are affected before you select Confirm Save.
- View members need Viewer-compatible roles. You can give a custom role to a View member only if its base is No Access or Viewer and no module is set to Editor. 8090 Software Factory rejects edits that would add Editor access to a role a View member or a pending View invitation holds.
- Admins always hold Owner. Organization Admins can only be assigned the Owner project role, so they can't be given a custom role.
What deleting a custom role does
Deleting a custom role also changes the access of everyone who holds it. 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. This can't be undone.
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. |
The QA Triager role has no Requirements access, so it cannot link themes to features.
Next, see the Permissions reference.