Add and remove a person
An admin adds a person by GitHub login. The person signs in and gets a user token. An admin removes a person with one command. The removal ends the person's tokens, agents, profiles and secrets.
Add a person
Remove a person
| After removal | Result | Code |
|---|---|---|
| The person's user token | HTTP 401 | fleet/internal/authn/authn.go |
| The person's identity token | HTTP 403 "not a member" | authn.go |
| A token of one of the person's agents | HTTP 403 | authn.go |
| The person's personal node | Heartbeat works, the node gets no turns | fleet/internal/node/coordinator.go |
Token kinds
| Token | Form | Who makes it | Ends |
|---|---|---|---|
User token, cli |
flu.<id>.<secret> |
fleet login, or fleet token mint --kind cli |
90 days, revoke, or removal |
User token, connector |
flu. |
fleet token mint --kind connector --scope read |
The same. Read scope calls only read tools of /mcp. In the header, or in the path: /mcp/k/<token>. The OAuth sign-in of /mcp mints one labelled oauth <app>. |
| Bootstrap code | flb. |
fleet token bootstrap, or install.sh |
One use, 1 hour. It binds the first admin. |
| Identity token | JWT | dex, after GitHub sign-in | Its own expiry |
| Owner token | hex in owner.token |
fleet serve --owner-token |
Remove the flag or the file |
| Agent token | <agent id>.<hmac> |
The server, for each turn (FLEET_TOKEN) |
Read-only on its own row after done or stopped |
| Join token | flj. |
fleet node token, --shared for an admin |
One use, 1 hour |
| Node token | fln. |
The server, at a join | No expiry, no revoke. A new server key ends it. |
- Roles: a fleet has
adminandmember. A project hasmaintainerandmember(fleet/internal/registry/registry.go). - The last active admin cannot step down or be removed. The last maintainer of a project is protected.
- Not built: a drain state for nodes. The design says "drain". The code only gives the node no more turns. The node token stays valid.
- Not cleaned up at removal: the person's project memberships and Telegram link. A removed
person's project membership cannot be removed through the API at this time, because the lookup
finds active users only (
fleet/internal/api/projectmembers.go). - Not built: a fleet id in the user token. A token of one fleet fails on another fleet because the database and the server key are different.
- Sign-in sequences in full: sign-in.