Skip to content

Managing users

The Users page (/admin/users) lists every account in your tenant:

User list with the status switch, role badges and search

Column Content
Status Active/inactive as a switch — effective immediately; your own account cannot be deactivated.
User name The sign-in name, with the full name below it in grey.
Email The email address, or “—”.
Roles Superadmin (yellow) or User (grey); additionally LDAP or SSO for directory accounts.
Groups Group memberships.
Created The creation date.
Actions Edit, Delete (except for your own account).

The search field filters live across the user name, email and name; long lists are paged (50 per page). If a directory service is configured, “Synchronise users” triggers an immediate comparison (the chapter “Settings → Directory service”); otherwise the button leads to the settings.

“New user” opens the form (/admin/users/new):

Editing a user, with the form and the access overview

Field Meaning
Active Only active users can sign in — and only they occupy a licence seat.
User name The sign-in name; cannot be changed once the account is created.
Full name The display name, “Erika Mustermann” for example (optional).
Email Optional; checked for validity.
Password Mandatory when creating; when editing, “empty = unchanged” applies. Must satisfy the password policy.
Default language The user’s interface language; “Default” inherits the tenant language. The user can change it in their profile.
Superadmin Full administration rights in the tenant — superadmins bypass the permission system entirely.

Example — creating a case handler:

  1. Click “New user”.
  2. Enter the user name e.mustermann, the full name Erika Mustermann, an email address and an initial password.
  3. “Save” — then assign a project through Access (the chapter “Access and roles”).

For directory accounts (LDAP/OIDC) the name and password are locked — they are taken from the directory at the next sync; a note at the top of the form points this out.

In edit mode the “Access overview” card shows (read-only) the user’s effective roles per project and level; for superadmins it says “Superadmins automatically have full access to all projects.” The assignment itself is done centrally through “Manage access” → the Access page.

Delete removes the account after a confirmation (“Really delete user ‘…’?”). You cannot delete yourself. If the user has created legal holds, compliance protection prevents deletion. In practice, deactivating is usually the better choice: the account remains traceable but no longer occupies a licence seat.