Users and roles

Three kinds of users sign in to the panel: you and your staff run the panel, customers run their own servers. Users are managed under Users.

Roles

Admin — everything.
Staff — only what their permissions allow. With no server permissions they see their own servers and the ones opened to them, like a customer.
Customer — their own servers and the servers they've been given access to.

Customers don't create servers themselves — an administrator hands them out (see Your first game server) or your billing system does. Customer accounts are usually created by the billing system too; by hand only for tests and special cases.

Add a user

Users → + Add user: e-mail, password and role. A staff member starts with no permissions — grant them on the Permissions tab of their card.

The list shows the role, the number of permissions a staff member has, a without 2FA mark, the last sign-in and activity. Filter by role and search by e-mail above the list.

Staff permissions

A staff member's card → Permissions tab. Permissions are grouped:

Game servers — view all servers; manage all servers (start, console, files, backups, settings, deletion, owner, plan, suspension).
Users — view users; manage users (create, disable, change role, reset password and second factor, end sessions); grant permissions to staff; audit log.
Infrastructure — view nodes; manage nodes; locations; S3 storages; database hosts.
Catalog — game catalog; maps and mods; plans.
System — webhooks; panel settings.

Preset buttons tick a typical set: Support, Billing, Content, Engineer, Senior staff. A preset only ticks boxes — adjust them afterwards. The panel asks for confirmation for extended permissions. Save with Save permissions.

Admin-only, never granted to staff: modules, API keys, the panel backup, the two-factor policy and the Admin role itself.

A staff member can't become more powerful than they are: they grant only permissions they have themselves and don't touch administrators or colleagues holding permissions they lack. Only an administrator can change those.

Managing an account

On the user's card:

Change role. A staff member who stops being staff loses their permissions.
Reset password — set a new password; all of the user's sessions end.
Two-factor authentication → Reset (Access tab) — when the user has lost their phone and recovery codes. They sign in with the password and, if the second factor is required, set it up again.
Active sessions (Access tab) — where the user is signed in now; End all signs the user out everywhere.
Disable — the user can't sign in and active sessions stop working. The account and its servers stay; Enable restores access at any time.
Sign in as — see the panel as the user does, for example to see exactly what a customer sees. A bar at the top offers the way back to your own account. The sign-in is logged in the audit log under your name, actions inside under the user's.

The card's tabs: Servers — the user's servers; Access — sessions, second factor, issued API keys and access to other people's servers; Audit — the user's latest events and actions on the account.

Access to a single server

A server's owner (or an administrator) can open it to another user — a friend, a moderator, a helper — without handing the whole server over. The server's page → Access tab: the user's e-mail and permission boxes:

View, Launch, Stop, Restart, Console, Logs, Statistics, Deletion, Backups, Files, Parameters, Reinstall, Maps and mods, Schedule, Databases.

The user needs a panel account — access is granted by e-mail.
Granting again to the same e-mail replaces the whole set of permissions rather than adding to it.
Parameters lets them change only the settings marked "owner"; "admin only" ones such as slots stay closed.
Passwords and other server secrets are visible only to the owner and administrators.
A co-owner can't pass access on: the Access tab exists only for the owner and administrators.

Only an administrator changes the owner itself: the server's Settings tab → Owner → Change. The previous owner loses all access; backups, files and tasks move with the server.

Second factor. Everyone turns it on in their own profile. Under Settings → Security you can make it mandatory for administrators and staff — then nobody signs in without it.
Brute-force protection. After several failed sign-in attempts the IP address is blocked for a while.
Audit log (Access → Audit log) — who did what and when: sign-ins, changes to users and permissions, actions on servers.