How to OP a Player & Manage Permissions in Minecraft
Give admin rights safely with /op, LuckPerms, and group ranks. Java + Bedrock commands included.
What /op actually does
/op <player> gives a player full operator rights — every command, every permission, no restrictions. It's the nuclear option. Useful for the server owner; dangerous for everyone else.
Quick way (small servers)
From the console (FreeMCHost panel → Console), type:
``
op YourUsername
``
To remove:
``
deop YourUsername
``
You can also edit ops.json directly with the username and a UUID lookup.
Bedrock equivalent
On Bedrock, use the same console command:
``
op YourUsername
``
Or set permissions levels in permissions.json (operator, member, visitor).
The right way for >2 admins: LuckPerms
/op has no nuance — your moderators don't need world-edit-everywhere. Install LuckPerms (see [Best plugins 2026](/blog/best-minecraft-plugins-2026)) and create real ranks:
``
/lp creategroup admin
/lp creategroup mod
/lp creategroup helper
``
Then grant specific permissions:
``
/lp group mod permission set essentials.kick true
/lp group mod permission set essentials.mute true
/lp group helper permission set essentials.warn true
``
Assign players:
``
/lp user PlayerName parent set mod
``
A safe default rank ladder
- Owner — full
/op(you). - Admin — most commands except server stop / file edits.
- Mod — kick, mute, ban, tp.
- Helper — warn, mute, /tp to player.
- Player — default.
Common mistakes
- Opping everyone "just for now" — they keep the perms after restart. Use ranks.
- Editing `ops.json` while the server is running — gets overwritten. Stop the server first, or use
/opin console. - No audit trail — install CoreProtect so you know who did what.
Related
- [Best plugins 2026](/blog/best-minecraft-plugins-2026)
- [Anti-grief guide](/blog/minecraft-anti-grief-guide)
- [Install a Minecraft server](/blog/how-to-install-a-minecraft-server)