Admin tab: user management (roles/clearance)
AdminIn the Administration → Users tab you create accounts and control who may see and do what. The access logic behind it is explained in RBAC & confidentiality levels; this article describes the concrete fields and workflows.
Fields of a user
Section titled “Fields of a user”| Field | Meaning |
|---|---|
| unique identifier (login via OTP) | |
| Phone | optional (for OTP via SMS) |
| Name | display name |
| Role | Employee or Admin (Admin = full administrative access) |
| Knowledge roles | comma-separated roles that control vault access |
| Clearance level | numeric level; a user sees content up to their level (convention, e.g. 0 = public, higher = more confidential) |
| Department | organizational unit, optional for department filters |
| Active | reversibly deactivate an account |
Create a user
Section titled “Create a user”Via Create user you record email, name, role and optionally knowledge roles/clearance/department. The user then signs in passwordless via a one-time passcode (OTP). Setting up OTP (SMTP/SMS) is described in Set up OTP. Every active user occupies a seat of the license. → License & edition model
How the fields work together
Section titled “How the fields work together”Access results from role/knowledge role AND clearance level AND department against the requirements of the respective vault or document — all conditions must be met. This lets you specify, for example, that only the “Finance” role with clearance ≥ 2 can see a particular vault. The vault side of this: Vaults & indexing.
Limits & notes
Section titled “Limits & notes”- Admin-only. Only administrators manage users.
- GDPR: deleted users are anonymized (data removed, the record kept for audit integrity).
- There are exactly two roles (Employee/Admin); finer gradation happens via knowledge roles and clearance.