What is a sub-user?
A sub-user is someone you let help run your server without ever handing over your account. You invite them by email, tick exactly what they are allowed to touch, and they manage those parts through their own login. It is how a server stops being a one-person job: co-owners, admins, builders, and moderators each get their own access, and you never have to share a password to make it happen.
Inviting someone to your server
Inviting is quick. You open the invite form, enter the email of the person you want to add, choose which services they can use, and send it. They get an email with the option to accept, and once they do, they can manage the areas you allowed and nothing else. You stay in full control the whole time: you can change what a sub-user is allowed to do whenever you like, revoke their access in one click, and cancel an invite that has not been accepted yet.
Permissions are granular, not all-or-nothing
This is the part that makes sub-users genuinely safe to use. You are not flipping a single "trusted" switch. Every area of the server is its own permission, and most split into a view level and a manage level, so you can let someone watch the console without letting them run commands, or let a builder edit files without letting them delete anything. The full set of areas you can grant:
| Area | What granting it allows |
|---|---|
| Server Info | View the overview, and optionally renew the server |
| Console | Watch the console, send commands, and use power controls |
| File Manager | Browse and download, edit and upload, or delete files |
| Databases | View database details, or create and manage databases |
| Schedules | View scheduled tasks, or create and manage them |
| Backups | View and download, create, or delete and restore backups |
| Network | View allocations, or add and manage ports |
| Startup | View startup parameters, or edit them and the Docker image |
| Versions | Browse versions, or install and change the server version |
| Properties | View server.properties, or edit its values |
| Mods & Plugins | Browse mods and plugins, or install and remove them |
| Settings | View SFTP and server info, rename, or reinstall the server |
Give the least access that gets the job done
Because the permissions are this fine-grained, the smart way to use them is to grant only what a person actually needs. A builder needs the file manager, not the reinstall button. A moderator needs to send console commands, not to manage your databases. Handing everyone full access is the quickest way for a well-meaning helper to break something by accident, or for one compromised account to take the whole server down with it.
Keep the dangerous permissions, Delete Files, Delete and Restore backups, and Reinstall, on the shortest possible list of people. Most of your team never needs them, and the ones who do should be the people you would trust with the server on their worst day.
The other side: servers shared with you
Sub-users works both ways. When someone else adds you to their server, it shows up here under My Access, along with who owns it and exactly which permissions you were given. So this one page is both the place you hand out access to your own servers and the place you keep track of every server other people have trusted you to help run.
Tools that help a server team work together
Sub-users decides who can touch the panel. It does not, on its own, organize the people, and a server with a real staff team usually leans on a few outside tools to keep everyone moving in the same direction. None of these are part of the panel; they are just what most communities end up using alongside it:
- Discord for talking to your team, sorting staff into roles, and handling reports and applications
- A password manager like Bitwarden or 1Password for sharing any credentials safely, so passwords never get dropped into a chat
- A task board like Trello or Notion for tracking who is building what and which jobs still need doing
- GitHub for version-controlling configs and plugin setups, so a bad change can always be rolled back
The pattern is simple. Sub-users and their permissions keep the server itself locked down to the right hands, and tools like these keep the humans around it organized. Put both together and a server runs like a team instead of a to-do list that all lands on you.