Govern access
This section is for administrators. It covers accounts, roles and permission lines, row scopes, field visibility, sign-in policies, machine access, the audit trail, rollback, retention, and the rules for apps and the assistant.
Start with the identity pages, then the authorization pages, then the assurance pages. Each page stands alone; the cross-links fill in the model.
Identity
Section titled “Identity”- Manage accounts — the account document, the status lifecycle, first credentials, delete and restore.
- Roles and permission lines — the line grammar, the named actions, and the guard that bounds every role write.
- Assigning roles and role election — put roles on accounts, and how one role is elected per request.
- Enforcing MFA — the TOTP factor, the two enforcement levels, and recovery.
- Single sign-on with OIDC — provider documents, JIT provisioning, and single sign-on only mode.
- Sessions, refresh tokens and lockouts — token lifetimes, rotation, and the login throttle.
- Machine access: API keys — static keys pinned to one account and role.
Authorization
Section titled “Authorization”- Row scopes — narrow a permission line from whole doctypes to matching rows.
- Field visibility with tags — hide fields per role on reads, writes, and in the audit log.
Assurance
Section titled “Assurance”- Auditing activity — read the mutation log and the login-event log.
- Rolling back changes — undo to an earlier mutation, restore a delete, and the limits.
- Retention — what each data class keeps, and for how long.
- Controlling app reach (grants) — bound what an external app may attempt.
- Governing the assistant — availability, token budgets, instructions, and tool behaviour.
Related
Section titled “Related”- Security & governance overview — the evaluator summary of this model.
- Roles, levels and the authority guard — the concept behind the guard.