Guide 49 of 61 · Running a fleet with Central Lite
Give people the right access in the console
Give each Central Lite admin one of six roles, for the whole org or a host group, and know who may request a kill order and who holds each approver key.
Built, not yet claimed preview: this guide describes a package that has not passed its release gate.
Learn the six roles and what each sees, make host groups, bind roles by hand or from your identity provider's groups, know who may request a kill order, keep track of who holds each approver key, and know what Central Lite's host can do outside all of it.
1. Know the roles and what each sees
Every console admin holds one or more of six built-in roles; there are no custom roles. owner can do everything, including roles, single sign-on, SCIM and SIEM settings. admin publishes policy, runs rollouts, makes enrolment tokens, revokes machines and changes compliance settings. security requests, cancels and lifts kill orders, stops single tasks, and works incidents and evidence exports. auditor reads everything, Central Lite's audit log and timelines included, and may export evidence, its only write. finops sees costs, budgets and spend by person. viewer sees the fleet's inventory, health, rollouts and costs, but nothing personal.
Seeing people is a permission of its own: names, identities at your provider, a timeline's person-level view and evidence exports need it, and viewer and finops don't have it. The console lists only the sections your roles open and offers only the changes they allow, and Central Lite checks every call itself: one your roles don't allow is refused with “your roles don't allow this”. A role decides whether you may ask; every change still asks for your passkey. Admins who existed before roles were added are all owners, so nothing changes until you edit bindings.
2. Make host groups
A host group is a named, fixed list of machines; a machine may be in several. Groups live only in Central Lite and never reach the machines. garm-central group create makes one and group add puts a machine in it by its host id, which garm-central node list shows. Deleting or renaming a group is refused while a role is bound to it, while an SSO or SCIM role mapping names it (remove the mapping first), and while an unused enrolment token names it. In the console, Settings → Roles & access → Host groups makes, renames and deletes groups and adds and removes hosts, each with a passkey. An enrolment token made with --group puts each new machine in that group as it enrols.
A role bound to a group reaches only its machines. The inventory and its counts, costs by model, the machines' events, the live feed, pending approvals and kill orders show its machines only, and it may revoke one of them, ask for a kill order by host: or hosts:, and read or export a task's incident timeline when every machine the task ran on is in its group. What belongs to the whole org needs a role for the whole org: rollouts and policy, Central Lite's own audit log, costs by provider account or by person, enrolment tokens, and the settings.
garm-central node list
garm-central group create laptops
garm-central group add laptops --host <host id>
garm-central group listSee also
Enrol developer machinesEnrol a machine in Central Lite with a one-time token that pins Central Lite's key, see it report in the inventory, and let its users enrol presence keys.
3. Bind roles by hand or by group
garm-central role bind gives an admin a role at a scope: org (the default), group: and a group's name, or host: and a host id. garm-central role list shows each binding with its id and where it came from, and role unbind removes one by its id. In the console, Settings → Roles & access lists the bindings with their source and since when, removes one, and binds a role to a listed admin, each with a passkey; an admin who holds no binding yet is bound on the host, since the console has no admin list.
From your identity provider, a group can carry a role two ways: garm-central sso map sets it at each sign-in from the token, and garm-central scim map sets it as SCIM sends the group's members. Central Lite refuses to remove the last owner binding held by an admin with a passkey, and warns while only one is left: keep two.
garm-central role bind --admin alice --role security
garm-central role list --admin alicegarm-central role unbind --binding <binding id>See also
Sign in to the console with your identity providerLet admins open Central Lite's console through Okta, Entra ID or another OIDC provider, with roles from its groups and a passkey still behind every change.
4. Know who may request a kill order
Requesting, cancelling and asking to lift a kill order need security or owner at a scope that covers the order. A security role bound to a host group may request or cancel an order by host: or hosts: for machines in its group, and sees only those orders; an order for the whole fleet, an agent or a person, and asking to lift any order, need the role for the whole org. Answering a remote approval on the Approvals page needs owner, admin or security (one bound to a group answers its machines' only), and still the approver key.
A role never approves anything: kill orders and remote approvals are signed by approver keys, listed in the org root. Releasing a legal hold counts only admins holding owner, or security for the whole org, with a passkey, each from 24 hours after the binding. Placing a legal hold and asking for its release are done on the host, outside roles, for now.
See also
Stop agents across a fleetSuspend, terminate or lock down agents on one machine, one agent, one person or the whole fleet, with an order two approver keys sign and each node checks.
5. Keep track of who holds each approver key
Central Lite records which admin holds each approver key: the admin signed in when the key first answers in the console, or the one you name with garm-central approver hold. It then refuses that key from anyone else's session. garm-central approver holders, or Incidents → Approver holders in the console, shows each key's holder, since when, whether it is suspended, and how many keys can still sign against the threshold a fleet-wide order needs.
When your identity provider deprovisions a holder, Central Lite stops counting their keys at once. A machine still accepts them until the key is revoked: Central Lite revokes a key still suspended after 7 days, or at once when the holder is deleted, unless that would leave fewer keys than a fleet-wide order needs; then it waits for an owner (alert approver_revocation_waits). An owner can revoke a suspended key at once with “Revoke with a passkey”; revocation is permanent. While suspensions leave too few usable keys, Central Lite raises approvers_below_threshold; single-task kills and root's local lift still work. garm-central approver sweep does now what serve does every hour.
garm-central approver hold --key-id <approver id> --admin alice
garm-central approver holdersSee also
Provision and remove people with SCIMLet Okta or Entra ID create the people Central Lite knows, give them console roles from their groups, and end their access when they leave.
6. Use the host's commands as break-glass
Roles and single sign-on limit what a console session or an identity provider can do, not what Central Lite's host can. Every garm-central command runs as the account that holds Central Lite's keys, outside roles, and is chained in the audit log with that account's name. That makes it the way back in when every owner is locked out: bind an owner again with role bind, or print a recovery code with admin recover.
It also means whoever controls that host can add admins and, under Central Lite's single software root, approver keys. Guard the host and its account as you guard your owners.
garm-central role bind --admin alice --role owner
garm-central admin recover --name aliceSee also
Stand up Central LiteSet up Central Lite on one Linux host: its org and keys, its HTTPS port, a first admin and a backup passkey, and its first encrypted backup.