Role Delegation & Step-Up Authentication #
Platform access on https://admin.<your-domain> follows strict Role-Based Access Control (RBAC). Roles are enforced server-side in control-backend; UI menu hiding is strictly cosmetic.
Platform Roles Matrix #
| Role ID | Display Name | Capabilities | Restricted From |
|---|---|---|---|
super_admin | Super Admin | Full platform access: user invites, role grant/revoke, storage config, ops, alerts, recovery, upgrades, audit | Reading tenant email bodies/attachments (ADR-0025) |
operator | Platform Operator | Service list/logs/restart, alert inbox (ack/snooze/resolve), maintenance windows, offline upgrades/rollbacks | Role delegation, storage driver mutation |
storage_admin | Storage Admin | Storage backend configuration & capability probes (/v1/platform/storage/*), backup/recovery jobs | Role delegation, platform user invite |
auditor | Global Auditor | Read-only /v1/platform/audit, /v1/platform/users, /v1/audit/verify | All mutations, service restarts, config writes |
Delegating Roles to Team Members #
- Navigate to Access & Role Management in
https://admin.<your-domain>. - Invite Platform User: Provide the operator's
loginand select initial roles (for example,operatororauditor). - Share the generated
enrollment_token(valid for 24 hours) via an out-of-band secure channel so the operator can enroll their own Passkey onhttps://admin.<your-domain>. - Grant / Revoke Roles: Super Admins can adjust roles dynamically. Changing roles requires an active
AAL2Passkey session.
IMPORTANT
Last Super Admin Protection: control-backend refuses to revoke super_admin or deactivate an account if doing so would leave zero active super_admin accounts (ErrLastSuperAdmin).
Step-Up Re-Authentication (AAL2) #
High-risk operations require a recent step-up Passkey assertion:
- Restarting critical services (
postgres,identityd,control-backendd,smtp-in,mta-out) - Triggering backup/restore jobs or offline release upgrades/rollbacks
- Modifying storage configuration or generating MFA recovery codes
- Granting or revoking platform roles
Every step-up action also validates a mandatory non-empty operational reason (>= 5 characters) and rejects any target or reason referencing mail content (body, payload, message_content, attachment, rfc822).