Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
How-to guide

Manage team members and roles

Invite a person, assign a role and a business unit, and keep validators separate from authors.

5 minFor: Workspace owner

Team management is on Settings (/settings), tab Team & roles. Only an Administrator sees it. Every change here is audited.

Invite a person

  1. On Team & roles, open Invite a teammate.
  2. Enter Full name and Work email, pick the role, and send.
  3. The person gets a one-time invitation link. Opening it sets their password; the link carries its credential in the fragment, so it never reaches a server log.

Expected result

The roster lists the person with the role you chose. Until they open the link the row offers resend and revoke; after, deactivate and reactivate.

Note

A person provisioned by single sign-on arrives as SSO user, which is read-only until an administrator assigns another role.

Assign a role

Change the role on the person's row. The ten roles and what each may do:

RoleRights
AdministratorAll workspace data; users, security, sources, and reports.
Governance leadOrganization-wide governance, sources, canonical models, final attestation, and reports. No user administration.
Team leadAssigned business units only. No assignment means no access.
Model ownerOwned AI systems; register systems, link models, and submit evidence.
ContributorAssigned business units; contribute and submit evidence but cannot approve it.
ValidatorOrganization-wide independent evidence review. Cannot validate their own work or final-sign.
AttestorOrganization-wide read, final attestation, and Board and Audit report generation and download. No raw retained GL download.
AuditorOrganization-wide read, audit log, raw financial evidence, and report download. No writes.
Read onlyOrganization-wide ordinary read. No raw financial-evidence download or writes.
SSO userProvisioning-only read access until an administrator assigns another role.

Every row above is read from the same role table the product uses, so this page cannot drift from it. The full matrix is in Roles and permissions.

Business units

Team lead and Contributor see only their assigned business units; no assignment means no access, and the roster says so. Assign units on the person's row. Organization-wide roles show All business units. Model owner is scoped to the AI systems they own instead.

Separation of duties

The role table keeps three things apart, and the product enforces it rather than asking you to remember:

  • A Validator confirms GL evidence but cannot validate their own work and cannot final-sign.
  • A Contributor submits evidence but never approves it.
  • An Auditor reads everything, including the audit log and raw financial evidence, and writes nothing.

The Team & roles tab shows a read-only segregation-of-duties reference beside the roster. The same sets are mirrored in the backend, and a test fails when either side drifts.

Previous

Generate an audit pack

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.