How to Add Subusers, and What the Permissions Actually Mean

If you run a server with co-admins, moderators, or a dev helping with plugins, you don't have to hand out your own login. Subusers let you invite other RepublicNodes accounts to manage your server with exactly the access you choose.

How to Add One

1. Go to your service's Users (or Subusers) tab.
2. Click Add Subuser and enter the email address of the account you want to invite (they need an existing RepublicNodes account).
3. Select which permissions to grant — see below.
4. Save. They'll see the server appear in their own dashboard immediately, scoped to only what you allowed.

What the Permission Groups Actually Control

• Control — start/stop/restart/kill the server. The basic power controls.
• Console — view live console output and send commands. This is a big one: console access effectively means admin-level control over the game/software itself (they can run any command your server accepts), even without other permissions.
• File access — browse, edit, upload, download, delete files. Give this only to people you trust not to break configs or accidentally delete something important.
• Backups — create, download, restore, delete backups. Restore access in particular can overwrite everything currently on the server.
• Databases — view credentials, create/delete databases.
• Schedules — create and manage automated tasks.
• Network — view and modify allocations/ports (on plans where that applies).
• Startup — change server version, edit startup variables, switch eggs (where the Egg/Game Changer is available).
• Settings — rename the server, change its icon/description.

A Practical Approach

Don't just grant everything by default. A good pattern:

• Moderators: Console only (so they can run in-game admin commands) — nothing else.
• Co-owner / trusted admin: Control, Console, Files, Backups.
• A developer helping with plugins: Console, Files — skip Backups/Settings unless they specifically need it.

Removing Access

Go back to the Subusers tab and remove them at any time — access is revoked immediately, no confirmation needed from their end. This is worth doing promptly if someone stops helping with the server or a falling-out happens; there's no reason to leave standing access around.

Subusers are the right way to share server management — it keeps your own login private, gives you an audit trail of who has what, and lets you scale back access instantly if you need to.