// Benutzung · Zugriff & Rollen
Managing users & roles
Create people, give them roles, and define what a role can do — from the Access page.
The Access tab appears only for admins (anyone holding
iam.manage). All of this is also reachable via the auth-svc CLI, which is how the first admin is bootstrapped before any UI exists.
Add a user
- Open Access → Users → New user.
- Enter a username, email, and password. Optionally grant an initial role and choose its scope — Global (all locations) or one specific location.
- Create user. They can log in immediately.
Set a new password later with the Password button on the user's card; delete the account with Delete (you can't delete your own).
Assign or remove a role
- Assign role on a user's card → pick a role and a scope (Global, or a single location) → Assign. Assigning the same role twice for the same scope is a no-op. Only an existing location can be picked; through the API, an assignment for a location id that does not exist is refused, also when the user already holds it for a location deleted since.
- Each assignment shows as a chip with its scope (a globe for global, a pin for a location). Click the on a chip to unassign just that grant.
- A dashed chip marked grants nothing is an assignment stored before Fleeger
refused its location (for example
"*"or""): it gives the user nothing. Remove it and assign the role globally or for a location instead.
A global assignment applies everywhere; a location assignment applies only there. See Delegating a location for the common "let someone run just one site" recipe.
Define a custom role
Built-in roles (admin, operator, viewer) are locked. For anything else,
create a role:
- Access → Roles → New role.
- Name it (e.g.
homelab-operator). - Tick permissions from the catalog — grouped by area (Locations, Resources,
Control, Alerting, Audit, Administration), plus
*for a superuser role. - Create role. Edit its permissions later with Edit; Delete removes it and unassigns it from every user. If another admin saved the role while you were editing it, your save is refused rather than undoing theirs: the editor then shows the role as it now is, and you tick your change again.
Permission groups marked location-scopable (Locations, Resources, Control) are
the ones worth assigning per-location. iam.manage, alerting and audit permissions are
always effectively global.
Resources includes resource.allow_invalid_certs: a saved credential on a
resource whose TLS certificate checks are off (a Proxmox or iDRAC with a
self-signed certificate). Give it at the locations where that is wanted;
resource.edit does not include it, resource.* and * do. See
self-signed TLS.
Every change is in the audit log
Each change on this page (a user created, edited, its password reset, its sessions ended or deleted; a role assigned or removed; a role created, edited or deleted) is recorded in the hub-wide audit log: who did it, from which address, what it was before and after. Passwords are never recorded, only that one was changed. While the audit log cannot record a change (inventory-svc down or not yet upgraded) the change is refused with 503 and nothing is changed; try again once inventory-svc is back. Signing in is not affected.
What each permission means
| Permission | Grants |
|---|---|
location.view/create/edit/delete |
see / add / edit / remove locations |
resource.view/create/edit/delete |
manage resources & credentials |
control.view |
see the control panel, and the control rows of the audit log for that location |
control.execute |
issue control actions (power a VM, reset a server) |
alert.view/create/edit/delete |
manage alert rules, channels, mutes |
audit.view |
read the whole hub-wide audit log (Audit page; always global) |
hub_logs.view |
read the hub's own logs: its services' (the Services page's log tail, which also needs resource.view held globally) and, on Kubernetes, its pods' (always global; a viewer or operator does not see them). Without it, a hub pod's Logs on the location page come back empty, with a note saying they need hub_logs.view |
iam.manage |
manage users, roles, and assignments (this page) |
* |
everything |
See RBAC & per-location access for the enforcement model.