Subusers & permissions

Give moderators, builders or co-owners access to your server without ever sharing your password. Every subuser gets their own login, scoped to exactly the permissions you grant.

Why use subusers?

The temptation when running a community is to just hand a trusted friend your panel password. Don't. Subusers exist so you can:

• Let a moderator restart the server without giving them billing access.
• Give a plugin developer console + files, but not the power to delete backups.
• Onboard a builder with file access to /world only, no console.
• Revoke access in one click when someone leaves the team — no password rotation needed.

Creating a subuser

From your server dashboard:

1. Open the Users tab in the left rail.
2. Click New Subuser.
3. Enter their email address.
4. Tick the permission boxes you want to grant (see the next section).
5. Click Create.

They'll get an email with a link to set their own password. They log in at panel.pulsarservers.com using that email and see only your server.

Permission groups

Permissions are grouped into categories. Within each, you grant individual actions:

Control

• Console — read live console output.
• Send Commands — type into the console.
• Start / Stop / Restart — power actions.

Files

• Read — list directories and view file content.
• Read Content — open files in the editor (depends on Read).
• Create — upload, new file/folder.
• Update — edit existing files.
• Delete — remove files. Granting this without backups permission is risky.
• Archive — zip / unzip operations.
• SFTP — use SFTP credentials (subuser can edit files in their own desktop client).

Backups

• Create / Read / Delete / Download / Restore

Schedules, Users, Databases, Allocations, Settings, Activity

Each has its own Create / Read / Update / Delete subset. Most are self-explanatory; the important one to watch is Users → Create, which lets a subuser add more subusers — only grant to true co-owners.

Common role recipes

Three roles that cover 90% of teams:

Moderator (restart + console)

• Control: Console, Send Commands, Start, Restart
• Backups: Create
• Activity: Read

This lets a mod restart the server when it lags, kick or ban via console, and create a backup before a sketchy event — but they can't touch files or invite others.

Plugin developer

• Control: Console, Send Commands, Restart
• Files: Read, Read Content, Create, Update, Archive, SFTP
• Schedules: Read

Full plugin iteration loop — upload jars, tweak configs, restart, watch console — without delete or backup powers.

Co-owner

Tick the Select all box at the top of every section. Equivalent to your account, minus billing access (subusers never see billing).

Editing or removing a subuser

From the Users tab:

• Click a subuser to edit permissions — changes apply on their next page load.
• Click the red trash icon to revoke access immediately. They'll be logged out within seconds and your server disappears from their list.

Audit log

Every action — yours and your subusers' — is recorded in the Activity tab. You'll see who did what and when: file edits, restarts, backup deletions, permission changes. Check it first whenever something on the server changes and you don't know why.