// Benutzung · Zugriff & Rollen
Delegating a location
Give someone control of one location without granting anything elsewhere —
the core of Fleeger's per-location RBAC. Worked example: let alice start/stop
VMs and power servers at homelab, and nowhere else.
You need
iam.manage(admin). Concepts and the enforcement model: RBAC & per-location access.
1. Create a controller role (once)
The built-in roles don't include control permissions, so make a custom one that covers both seeing the location and acting on it:
- Access → Roles → New role, name it
controller. - Tick
location.viewandresource.view(so they can see the location and its resources), and under Control:control.viewandcontrol.execute. - Create role.
2. Assign it for the one location
- Access → Users → create alice (or open her card).
- Assign role →
controller, scope homelab → Assign.
Her card should show one chip: controller homelab. That single scoped grant
is enough — reads are filtered per-location, so she'll see a dashboard
containing only homelab, and can control it.
3. Verify the boundary
- As alice, the dashboard lists only homelab; its metrics and reachability
show; a VM's Start/Stop works and lands in the audit log as
alice. - Other locations don't appear for her at all, and a direct control call against
one returns 403 (
Missing permission: control.execute at location '<id>'). - Her metric queries are pinned to homelab server-side (VictoriaMetrics
extra_filters[]), so she can't read another location's series even by crafting a raw query.
Notes
- To also let her manage alerts or see the control-plane's own (
meta) metrics and service logs, grant the relevant permission globally — those aren't per-location. - To widen her remit, assign
controllerfor another location too — each location is a separate grant. - To revoke, click the on the
controller homelabchip. - Managing users/roles is never delegable per-location:
iam.manageis global, so a location controller cannot escalate by editing roles.