Give staff the right tools on a Minecraft server

A staff team needs enough power to deal with trouble and no more than that. Here is how to split ranks, which commands each tier actually needs, how to log what staff do, and how to remove someone's access cleanly when they leave.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

Why op is the wrong tool

Vanilla gives you one switch: a player is op, or they are not. An op can /give themselves anything, teleport anywhere, change gamemode, ban anyone and, by default, run /stop. Ops also bypass plugin permission checks, so an opped moderator silently has every plugin's admin commands too.

So op is fine for you, the owner, and wrong for everybody else. The moment a second person is helping, you want permission groups, which is what setting up permissions with LuckPerms covers. How to op yourself is still the guide for your own access.

Three tiers is usually enough

Most servers converge on something like this. Name them what you like.

Helper. Here to answer questions and deal with the obvious: /kick for clear cases, /mute for chat problems, /tp and /tphere so they can go and look, /vanish so they can watch without changing behaviour, spectator mode for watching a suspected cheater, and CoreProtect inspect and lookup so they can answer "who broke this" without asking you.

Moderator. Everything a helper has, plus /ban, /tempban and /unban, your punishment plugin's commands, and whitelist add and remove.

Admin. Everything above, plus plugin configuration and reloads, world editing tools, CoreProtect rollback and permission group changes.

And then there is you. Three things stay with the owner: panel access that can restore a backup, reinstall a server or change the plan; the ability to grant permissions to the admin group, because whoever edits permissions can give themselves anything; and anything that deletes data irreversibly. The reasoning behind that split is in staff permissions and least privilege.

Vanish and spectate: the two tools that catch the most

A moderator who teleports to a reported player, visible and in survival, learns nothing. Everyone behaves when staff arrive.

Vanish (/vanish, usually from EssentialsX) makes a staff member invisible and takes them out of the player list and the join messages, so they can watch and follow someone around. Setting up EssentialsX covers the essentials.vanish node.

Spectator mode (/gamemode spectator) lets staff fly through blocks and watch from any angle. For checking killaura or x-ray, this plus patience beats any plugin flag, and anti-cheat on a Minecraft server explains why.

Two house rules worth having. Vanished staff do not interact: no opening chests, no breaking blocks, no picking things up. And come out of spectator before you forget you are in it, which force-gamemode=true in server.properties handles on rejoin (editing server.properties).

Log what staff do

Not because you expect staff to misbehave, but because when something goes wrong you need to know what happened, and someone who knows actions are logged thinks twice.

You have four separate records, and you want all of them:

1. Block and container logs. CoreProtect records who placed, broke, opened and took, including staff, and it is the one that resolves disputes. Undoing griefing with CoreProtect covers it, and the point about installing it before you need it applies doubly here.
2. Admin command logging. The logAdminCommands gamerule writes admin commands into the server log. Leave it on: enabling command blocks and functions covers that gamerule and its noisier siblings.
3. The server log itself. The Console shows joins, leaves and commands live, and the log files on the Files tab keep the history: reading server logs covers searching them.
4. The panel's own record. The Activity page, under More, shows who started, stopped or changed what in the panel, including which invited user did it: the panel activity log covers reading it.

A punishment plugin with a history command is a useful fifth, because it answers "why was this player banned, and by whom" without a log search.

Panel access is separate, and narrower

Giving someone a rank in game does not give them anything in your GuavaHost panel, and it should not. If a staff member genuinely needs to restart the server or read the console, invite them as a sub-user on the People page rather than sharing your login. Permissions there are granular, grouped as Console & power, Files, Backups, People, Ports & network, Scheduled tasks, Databases, Startup settings, Server settings and Activity: giving a friend access with sub-users walks through the invite.

Start narrow. A moderator who occasionally needs a restart needs Console & power and nothing else. Files and Backups let someone take or wreck your whole server, so treat those as owner level, and nobody but you needs People, because whoever can invite people can invite themselves back.

Two-person rules for the destructive commands

Some commands cannot be undone by the person who ran them, so the convention that saves servers is simple: nobody runs one of these alone, and a backup exists first.

Write it down somewhere your staff can see, and make the rule "take a backup, say what you are about to do in the staff channel, then do it". Backups covers taking one on demand, which takes about a minute and has saved more servers than any policy.

Removing access when someone leaves

Staff turnover is normal, and doing this badly is how old staff come back and cause trouble. Work the list every time, in this order:

1. Take the in-game rank off. In LuckPerms, lp user TheirName parent set default, then check with lp user TheirName info that nothing else is attached, because individual permissions survive a group change.
2. Deop them. /deop TheirName in the Console. Op survives a rank change, and people forget it is there.
3. Remove them from any plugin's own staff list. Some plugins keep an admin list in their config rather than using permissions. Check your punishment plugin and your world edit setup.
4. Remove their panel access. Open the People page and remove the invited user, even if they never used it.
5. Change shared credentials. If they ever had the SFTP password, change it with Set SFTP password on the Settings tab, and change any database password or plugin token too. Shared secrets outlive an account removal.
6. Check what they did on the way out, with the Activity page and a CoreProtect lookup on their name. Five minutes, and if something is wrong you want to know while a backup still covers it.
7. Tell your remaining staff, so nobody reinstates them out of habit.

If the departure was not friendly, work through protecting your panel account and turn on two-step login.

Common questions

Should I just op my moderators?

No. Op gives full access to every vanilla command and makes them bypass plugin permission checks as well, so an opped moderator effectively has every admin command on the server. Permission groups let you hand out /kick and /mute without handing out /give and /stop.

Does an in-game rank give someone access to my GuavaHost panel?

No, the two are completely separate. Panel access is only given by inviting someone on the People page, where you choose exactly which permissions they get, so a moderator can have console and power access without seeing files, backups or billing.

How do I make sure a former staff member really has no access?

Work the removal list rather than relying on one step: clear their permission group, deop them, check for plugin config admin lists, remove their panel invite, and change any shared SFTP or database password they knew. The shared passwords are the part people forget, and the part that still works after everything else is revoked.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• staff
• moderation
• permissions
• minecraft
• java

Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support