Users & Roles

The four roles

Each is a superset of the one below.

Role	Can
Viewer	Read everything — dashboard, models, servers, clusters, alerts, audit log. Change nothing.
Operator	Plus start, stop and create servers, and download models. Day-to-day operation.
Admin	Plus users, API keys, configuration, licence activation, and revealing a stored key.
Superadmin	Plus the sealed-secret operations confidential computing uses.

Most people are operators. Reserve admin for those who should be able to change who has access.

Accounts vs API keys

Give an application an API key, never an account. Keys are scoped to inference and revocable individually, so rotating one disturbs nothing else, and a leaked key cannot change configuration. See API authentication.

First run

A fresh deployment asks you to create the first administrator in the browser.

There is no default password in the product. If LIFEBOAT_ADMIN_PASSWORD is unset the container generates one per install and writes it where the deployment can read it. A product that ships with known credentials is a product that runs with known credentials — that is the whole reason for the design.

Passwords

Users change their own from the menu at the top right. An administrator can reset another user’s from the Users page.

Locked out

Container: set LIFEBOAT_ADMIN_PASSWORD and restart.
Desktop: quit and start again — first-run setup re-runs if no account exists.

What is recorded

Sign-ins, user and role changes, key creation and every key reveal are all in the audit log. A reveal is deliberately possible and deliberately never quiet. See Audit log.