# Platform administration

Users, administrators, account status, and operation audits.

## Three platform roles [#three-platform-roles]

Regular users work in the developer console. Operations administrators handle applications, releases, support tickets, and business inquiries, and can view the account directory. Super administrators can additionally enable or disable users, change platform roles, and revoke sessions.

Platform roles are independent of the workspace owner / developer / viewer roles. Owning your workspace does not give you permission to administer the entire platform.

## First super administrator and login [#first-super-administrator-and-login]

Administrators can [sign in](/login) with an existing account. Developer registration is currently closed. [Contact our team](/en/contact) to discuss access.

**The first registered account automatically becomes a super administrator** and can open [User management](/admin/users). Later accounts are regular users by default and cannot gain administrative privileges through registration fields.

For an installation with existing accounts, `pnpm run setup` performs a one-time initialization using the earliest registered account. The initialization marker persists; subsequent registrations, restarts, or setup runs do not assign the first-administrator role again.

## Delegation and maintenance [#delegation-and-maintenance]

A super administrator can find another account in User management and change its platform role to Super administrator. The recipient's existing sessions are revoked, requiring a new login. Users can also be assigned the Operations administrator or Regular user role, but you cannot change your own role on this page.

Trusted local operators can use this recovery command to promote a specific registered account:

```bash
pnpm admin your-registered-email@example.com
```

The platform has no default administrator password and cannot reveal user passwords or recover API-key plaintext.

## User management [#user-management]

Search by name or email, filter by enabled status and role, and browse paginated results showing registration time, workspace count, and active-session count.

Disabling an account revokes its sessions and the API keys it created. Re-enabling it does not restore revoked keys. Changing its role also revokes existing sessions and requires a new login.

You cannot change your own privileges or disable yourself through User management, and the last active super administrator cannot be removed. Operations are recorded in the internal audit log.

## Before launch [#before-launch]

Administrative permissions must be verified on the server. The platform provides authenticator TOTP and recovery-code workflows but does not automatically require every administrator to enable them. Enable and validate them for administrators before production and configure controlled access. First-account registration, role delegation, account disabling, and recovery must also be verified in the actual deployment.
