Reference
Roles and permissions
The ten workspace roles, what each may read and change, and the scope its records are limited to.
5 minFor: Workspace owner, Finance reviewer
Ten roles. The backend is the enforcement authority; the table below is read from the same role catalogue the product's screens use, and a backend test fails when the two drift. An administrator can assign every role but SSO user, which provisioning assigns.
Roles
| Role | Id | Rights | Practice |
|---|---|---|---|
| Administrator | admin | All workspace data; users, security, sources, and reports. | Yes |
| Governance lead | governance_lead | Organization-wide governance, sources, canonical models, final attestation, and reports. No user administration. | Yes |
| Team lead | team_lead | Assigned business units only. No assignment means no access. | Yes |
| Model owner | model_owner | Owned AI systems; register systems, link models, and submit evidence. | Yes |
| Contributor | contributor | Assigned business units; contribute and submit evidence but cannot approve it. | No |
| Validator | validator | Organization-wide independent evidence review. Cannot validate their own work or final-sign. | No |
| Attestor | attestor | Organization-wide read, final attestation, and Board and Audit report generation and download. No raw retained GL download. | No |
| Auditor | auditor | Organization-wide read, audit log, raw financial evidence, and report download. No writes. | No |
| Read only | readonly | Organization-wide ordinary read. No raw financial-evidence download or writes. | No |
| SSO user | sso_user | Provisioning-only read access until an administrator assigns another role. | No |
Who can do what
| Action | Roles |
|---|---|
| Manage users (invite, roles, business units) | Administrator |
| Manage connections and sources | Administrator, Governance lead |
| Register AI systems | Administrator, Governance lead, Team lead, Model owner |
| Register a standalone model (org-wide canonical row) | Administrator, Governance lead |
| Change Scorecard records; save or delete a scenario | Administrator, Governance lead, Team lead |
| Author a value claim | Administrator, Governance lead, Team lead, Model owner, Contributor |
| Author ledger evidence | Administrator, Team lead, Model owner, Contributor |
| Validate a value claim (never their own) | Validator |
| Final attestation of a value claim | Administrator, Governance lead, Attestor |
| Read Board and audit reports | Administrator, Governance lead, Validator, Attestor, Auditor, Read only, SSO user |
| Generate Board and audit reports | Administrator, Governance lead, Attestor |
| Read the audit log and verify the chain | Administrator, Governance lead, Auditor |
| Download the audit archive | Administrator, Governance lead, Attestor, Auditor |
| Download raw financial evidence | Administrator, Governance lead, Auditor |
| Author assurance evidence (regulated module) | Administrator, Governance lead, Team lead, Model owner, Contributor |
| Review assurance evidence and findings | Administrator, Governance lead, Validator |
| Run the readiness workflow (regulated module) | Administrator, Governance lead, Team lead, Model owner |
| Read records | Every role |
Lists are generated from frontend/src/lib/role-policy.ts, which mirrors the backend constants named in that file.
Scope
A role's scope limits which records its reads and writes can touch. The predicate is added to every query on the server; a record outside the scope answers 404, not 403, so its existence is not disclosed.
| Scope | Roles |
|---|---|
| Whole organization | Administrator, Governance lead, Validator, Attestor, Auditor, Read only, SSO user |
| Assigned business units | Team lead, Contributor |
| Owned AI systems | Model owner |