Managing Users
The Users page, under Administration, lists every account with its role, status and last sign-in, and shows how many of the license's seats are in use (Seats: 7 of 10 in use). Only administrators see it; other people can see only their own account.
Status
| Status | Meaning |
|---|---|
| Active | Can sign in. The card shows their email, role and when they last signed in (Never if they have not yet). |
| Invite pending | Invited and has not set a password yet. |
| No seat | Active, but the license has fewer seats than active users and this user was given a seat most recently: cannot sign in until a seat is free. |
| Inactive | Deactivated: cannot sign in. |
Search by name or email, and filter by role or status, including No seat. When every seat is in use, or the license has fewer seats than active users, a note under the seat count says what to do. If the list cannot be loaded, the page says so; choose Retry.
Changing a user
- Edit changes the name, email and role. The email must be valid and not used by another account.
- Deactivate stops the person signing in, and ends their open sessions on their next action: they are returned to the sign-in page with the reason. It also frees their license seat. Reactivate lets them sign in again and needs a free seat.
- Delete removes the account. Records it created, such as scripts and audit entries, are kept.
A role change applies to the person's next action, without signing them out.
Seats
Each active user holds one of the license's seats. Creating, inviting or reactivating a user when every seat is taken is refused with a message saying so; deactivate someone, or apply a license with more seats under Settings. If a license with fewer seats than active users is applied, nobody is removed: administrators keep their seats, the users given a seat most recently cannot sign in, and adding users stays refused until enough users are deactivated or more seats are applied.
Protecting administrator access
- No one can deactivate or delete their own account; another administrator must do it.
- The only active administrator cannot be deactivated, deleted or given another role. Make someone else an administrator first.
Passwords
Administrators never see passwords. A password reset by an administrator (through the API) must meet the password rule and ends the person's older sessions. People changing their own password must give their current one.
Audit
Every change is recorded in the Audit Log under the administrator who made it: INVITE_USER, RESEND_INVITE, CREATE_USER, UPDATE_USER (with the fields that changed), DEACTIVATE_USER, ACTIVATE_USER, UPDATE_PASSWORD and DELETE_USER. Passwords are never recorded.