Authentication
How sign-in and tokens work.
Signing in issues a short-lived access token, kept in a secure, HTTP-only session cookie. The web app sends it to the API for you.
API keys are for scripts. Create them on your Profile; each key is shown once, so store it safely. Only a fingerprint of the key is kept, so a lost key can't be recovered: revoke it and create a new one. The Profile shows each key's request count and last use.
Keys can run jobs and read your projects and the Registry. They can't create or revoke keys, change your password, or reach admin pages: those need a signed-in session. You can have up to 10 active keys, optionally expiring after 30, 90 or 365 days.
Disabled accounts cannot sign in, and their existing sessions stop working at the next request.