Roles & login¶
Signing in¶
- Open
/admin/login. - Enter your e-mail address and password.
- Wrong credentials show "Invalid email or password.". After five failed attempts within 15 minutes, the login is locked for 15 minutes for your IP address ("Too many failed sign-in attempts. Try again in about N minute(s)."). The operator can change these values with
AUTH_RATELIMIT_LOGIN_*.
Sessions last 12 hours. If your password or role was changed, you are signed out and must sign in again.
Warning
If every admin page shows the Bootstrap admin access notice, you are signed in with the password from the environment variable ADMIN_PASSWORD_HASH. This access only works while no database admin exists. Create an admin under Settings → Users, sign in with it, and then remove the variable.
ADMIN_BOOTSTRAP_DISABLED_AFTER (ISO date) turns the bootstrap access off from a given point in time, even if no database admin exists yet. The login then reports "Bootstrap access disabled — create an admin in the database.". How to get back in after a lockout is described in Auth & security.
Roles¶
Every user has exactly one role. In the role selection and in the header, the roles are called Admin, Servicemanager, Serviceowner and SLA Manager.
| Role | Can do |
|---|---|
| Admin | Everything: users, settings, notifications, API tokens, audit log, all services |
| Servicemanager | Operates all services: service status, outages, incidents, maintenance, internal notes and service configuration. Confirms outages in SLA reports. |
| Serviceowner | Sets the status of the services they are responsible for, creates incidents and maintenance for them, maintains their outages, incident updates, reviews and maintenance, enters the exact outage times of closed incidents, closes their incidents and maintenance, and confirms their outages in SLA reports |
| SLA Manager | Manages SLA schedules, holiday lists, targets and SLA reports. Maintains and confirms outages of all services and maintains incident updates, reviews and maintenance. Read-only otherwise. |
Who may do what¶
The table shows what the admin UI offers to each role.
| Task | Admin | Servicemanager | Serviceowner | SLA Manager |
|---|---|---|---|---|
| View dashboard, incidents, maintenance and settings | ✓ | ✓ | ✓ | ✓ |
| Set service status | ✓ | ✓ | own services | — |
| Edit and delete outages in the outage history | ✓ | ✓ | own services | ✓ |
| Create incidents and maintenance | ✓ | ✓ | own services | — |
| Incident updates and reviews, edit maintenance | ✓ | ✓ | own services | ✓ |
| Close incidents and maintenance | ✓ | ✓ | own services | — |
| Write internal notes | ✓ | ✓ | — | — |
| Exact outage times of closed incidents | ✓ | ✓ | own services | — |
| Create and configure services and groups | ✓ | ✓ | — | — |
| Assign responsible users | ✓ | ✓ | — | — |
| View and export SLA reports | ✓ | ✓ | ✓ | ✓ |
| Manage SLA schedules, holidays, targets | ✓ | — | — | ✓ |
| Start and generate SLA reports | ✓ | — | — | ✓ |
| Confirm outages in SLA reports | ✓ | ✓ | own services | ✓ |
| Notification setup, templates, subscribers, events | ✓ | — | — | — |
| Change settings, API tokens, users, audit log | ✓ | — | — | — |
"Own services" means the user is the responsible user of every affected component. If an action affects a component that someone else owns, it is refused; for report confirmations with "You can only confirm outages for your own services.".
All roles see the Service Status, Incidents and Maintenance menu items. The SLA manager sees the Service Status page and maintains outages there, but does not set a service status.
Info
If a button is missing, your role does not allow the action. If a button is visible but the action fails, the message explains why. The Create incident link on the Service Status page is shown to admins, service managers and service owners — for service owners only for their own services.
Managing users¶
Users are managed under Settings → Users (admin only).
- Create user: in the New user section, fill in Email, Name (optional), Password and Role, then click Create user. The password must be at least 8 characters ("Password too short"). The role defaults to SLA Manager.
- Edit user: in the list, change Name, Role and New password (leave it empty to keep the password) and click Save. The e-mail address cannot be changed.
- Change role or password: all existing sessions of that user end immediately, including your own if you change your own account. Changing only the name ends no sessions.
- Delete user: removes the account. You cannot delete your own account ("You cannot delete your own account."). The last admin can neither be deleted nor change role ("The last admin can't change role or be removed.").
- Internal notes of a deleted user remain and show "Unknown user" as the author. In the audit log, the stored e-mail address stays visible.