Adding Sub-Users

If someone else helps run the server — a co-admin, a friend who manages plugins — the Users tab lets you give them their own panel login instead of sharing yours.

Adding a Sub-User

Go to Users → New User
Enter their email address — click Invite User and they’ll get an invite to set their own password
Tick which permissions to grant, grouped by area

Permissions Are Granular

Sub-users aren’t all-or-nothing, and it goes deeper than one toggle per tab — each area breaks down into the specific actions within it. Control, for example, isn’t a single “Terminal access” switch: it’s four separate permissions (Console, Start, Stop, Restart), so you could let someone send commands without letting them stop the server, or vice versa. The same pattern repeats for Files, Backups, Databases, Schedules, Network/Allocations, Startup, and Settings.

A common setup is read/send-command access on Console plus Files, so someone can manage plugins and run commands without touching backups, billing-adjacent settings, or the ability to delete the server.

Warning

Whatever you grant access to, a sub-user can do with your server’s files and data — including deleting things, if you give Files access with delete permissions. Only add people you’d trust with an admin login on any system.

What Sub-Users Can’t Do

Account-level actions — billing, plan changes, deleting the server entirely, adding other sub-users — stay restricted to the account owner regardless of what permissions you grant.

Removing Access

Go back to Users, find them in the list, and remove them. Access is revoked immediately; no separate password reset or notification step needed.