Admin panel

The admin panel is available at:

https://builds.example.com/admin

The panel is for admins. Sign in with a name and password, or paste a token value; either way the name needs the admin role, and anyone else is turned away at the sign-in form. There is no separate admin login. See Permissions.

Everyone else works through the desktop app or the CLI, where the content roles (tester, developer, maintainer) decide what they can fetch and push.

The navigation contains:

• Dashboard: store, free-disk, and active-token cards; games; garbage collection; recent activity.
• Builds: streams and build status, with pinning and stream deletion.
• Users: invite people, reset passwords, and disable accounts.
• Tokens: create, inspect, and revoke service credentials.
• Access: manage role assignments and stream commit allowlists. See Users, tokens, and access.

Session security

The session rides an expiring session token in an HttpOnly, SameSite=Strict cookie scoped to /admin. The server revalidates it, and the admin role, on every request. Revoking the name's tokens, disabling the user, or removing the role signs the browser out immediately.

Always access the panel through HTTPS. Do not paste a session cookie or a raw token in screenshots, chat messages, tickets, or shared shell history.

Dashboard

The dashboard shows:

• Physical deduplicated store size and chunk count.
• Free space on the data volume.
• Number of active tokens.
• Build, stream, and pre-dedup content totals per game.
• Current GC retention policy and the last completed sweep.
• Recent activity with actor, action, game, and details.