Decide who may reach what
An access rule says: members of these identity-provider groups may log in to these hosts, as these local accounts, with this sudo. People need at least one rule to sign in anywhere.
Rules live under Admin → SSH access rules.
The parts of a rule
| Part | Meaning |
|---|---|
| Who | Identity-provider groups, or named identities |
| Hosts | Host groups and tags, which narrow the rule. A rule with neither is not limited at all: it covers every host |
| Accounts | The local accounts people log in as. %u means their own account |
| Sudo | The commands those accounts may run with sudo |
| Local groups | Local groups the account is put in, such as docker |
| AI may use these terminals | Whether people with this access may let an AI assistant type into their terminal. AI also has to be allowed for the host (off by default) — see Connect |
[!WARNING] Leaving both Host groups and Tags empty does not mean "no hosts". It means "do not narrow", so the rule applies to every enrolled host. A host matches when it is in any of the rule's host groups and carries all of its tags. Always set at least one unless you really intend a fleet-wide rule.
Their own account
%u gives each person their own account, named after their identity. Where the fleet allows it the agent creates the account. When the person loses access the account is locked; it is deleted only if you set Delete idle accounts after (days) in the fleet settings (off by default), and only if Keyreeve created it. The host's log then names a human being rather than a shared login.
Sudo is checked for you
When a rule grants a command through sudo, Keyreeve checks it against GTFOBins and tells you if that command is a known way to get a root shell — before you save the rule. Local groups that hand out root or secrets, such as docker, have to be confirmed explicitly.
Host groups
Hosts can be grouped, and groups carry settings of their own. Settings resolve host first, then the highest-priority group the host is in, then the fleet default. Group hosts under Admin → Host groups.
Temporary access
Access that should not be permanent is better asked for than granted. A temporary access policy (Admin → Temporary access, for hosts or Kubernetes) lets people ask for access for a window on the Temporary access page, routes the request to the approvers set under Admin → Role mappings → Who approves temporary access, and expires by itself — ending the sessions it opened when it does.
Changes apply at once
A rule change is pushed to every agent straight away (they also check in every 30 seconds). Removing access stops new logins and locks %u accounts at once; sessions that are already open carry on, except those opened through a temporary grant, which end when the grant does.

