Administrators, roles, and sessions

Create secure accounts, delegate limited capabilities, protect the owner, and revoke sessions.

Administrators

The section shows display name, email, roles, status, last login, and 2FA requirement. Adding a person asks for a display name, email, and initial password; the internal username is generated automatically. Their TOTP secret appears only once after creation so they can register it in an authenticator app. With permission, the editor can change their details or password, suspend or delete an account, and manage assigned roles or direct permissions.

Owner account

The first account created by the installer is the owner. It has every permission and cannot be deleted like an ordinary account. The panel prevents suspending the last active owner and protects higher-ranked accounts. Store owner credentials and the 2FA secret securely, with an off-panel recovery procedure.

Roles

A role has a name, description, hierarchy rank, and permission keys. The editor groups permissions by module, displays the exact key and description, and uses toggles. You can search for permissions and enable or disable groups. Hierarchy controls which roles and administrators someone may manage; permissions control the API operations they may perform. Remove a role's assignments before deleting it.

Sessions

An administrator can see current sessions with IP, user agent, last activity, and expiry, and revoke their own sessions. Revoking another user's session requires admin.sessions.revoke. Permission changes can invalidate sessions so capabilities refresh on sign-in.

Example access model