Op is the Global Admin of Minecraft. It grants almost every permission by default, and on a lot of small servers half the friend group has it because that was easier than working out what they actually needed.
If you work in identity and access management, setting up permissions on a server feels very familiar. LuckPerms, the plugin most widely used on servers, is role-based access control. Almost every feature in it has a direct equivalent in workplace IAM, and once you see that, it's much easier to work out how to set it up.
LuckPerms is role-based access control
A group is a role: a bundle of permissions you assign to players, the same way a role at work is a bundle of access you assign to people. You give permissions to the group and not to each player, so when something changes you change it in one place.
Parent groups are role inheritance. With parent add, a group inherits everything from the group below it, so mod can inherit from helper and you only add what's new at each level. At work this is nested groups, and it fails the same way. Something granted low down ends up everywhere above it without anyone noticing.
Every new player lands in the default group on joining, like the baseline access every employee gets on day one.
Tracks are the mover process. A track is a ladder like default → helper → mod → admin, and promote and demote move someone up or down it cleanly. The LuckPerms wiki points out that tracks don't affect inheritance. They're only a promotion route. You want the same for movers at work, a defined path between roles, so new access doesn't just pile up on top of the old.
Temporary permissions are time-bound access. settemp and parent addtemp give access that expires on its own after a duration like 1mo3d. That's time-bound access in the style of Entra PIM: you don't have to remember to take it away, because it removes itself.
With contexts, a permission only applies in certain circumstances, such as world=world_nether or server=lobby. That's Conditional Access. At work the conditions are locations, devices or apps, but the idea is the same: one person gets different access depending on where they are.
Negated permissions are explicit deny. permission set <node> false blocks something a parent group would otherwise grant, unless a node closer in the chain sets it back to true.
And the log is your audit trail. /lp log (with recent, userhistory and grouphistory) shows who changed which permission and when. At work that's the change history you'd check during an access review. /lp verbose shows every permission check as it happens, which is the closest thing you get to sign-in and authorisation logs when you're trying to work out why someone can or can't do something.
The commands below come from the LuckPerms command usage wiki.
A LuckPerms setup guide for a friends server
I'd start with five groups, each inheriting from the one below. default is the baseline: play, chat, set homes, basic commands. trusted is for regulars and adds a few extras on top, like more homes and /tpa.
Then the staff groups. helper can mute, warn and check logs, which is least privilege for a support role. mod adds kicks, temporary bans and rolling back griefing, so it's a scoped admin. admin manages plugins and LuckPerms itself. That's the privileged one, so keep it tiny.
Setting up the groups and inheritance:
/lp creategroup trusted
/lp creategroup helper
/lp creategroup mod
/lp creategroup admin
/lp group trusted parent add default
/lp group helper parent add trusted
/lp group mod parent add helper
/lp group admin parent add mod
Giving a group a permission, denying one, and limiting one to a world:
/lp group helper permission set <node> true
/lp group trusted permission set <node> false
/lp group mod permission set <node> true world=world_nether
The nodes depend on which plugins you run.
Making the promotion ladder and moving people along it:
/lp createtrack staff
/lp track staff append default
/lp track staff append helper
/lp track staff append mod
/lp track staff append admin
/lp user <player> promote staff
/lp user <player> demote staff
Temporary access, for example making someone a helper for an event weekend:
/lp user <player> parent addtemp helper 3d
And checking what happened:
/lp log recent
/lp log userhistory <player>
/lp verbose on
I'd do it in that order: groups and inheritance first, then permissions, then people. If you assign people first, you end up giving permissions straight to players "just for now", and that's how access spreads without anyone deciding it should.
Who should have op on a Minecraft server
As few people as possible. In vanilla Java, op has permission levels 1 to 4, and level 4 can run every command, including server management. On top of that, op sits outside LuckPerms. It's a vanilla mechanic, so it mostly walks past the groups you've built. Global Admin at work at least sits inside the identity system, which you can't say for op.
My rule is one or two people at most, used only for server maintenance and never for everyday play. Everyone else, admins included, gets exactly what their LuckPerms group gives them. If you need to do something your group can't, fix the group.
At work the equivalent is the break-glass account. It's locked away, and using it is an event. Companies keep the number of global admins small for the same reason (there's more on that in the post on IAM for growing mid-sized companies).
If I was building a server today, nobody would have the op permissions.
Where the comparison falls apart
There's no real identity layer. The Minecraft account is the identity, so there's no SSO, no MFA you control, and no HR system telling you someone left. You find out when they stop showing up.
It's also one system instead of 200. At work, the hard part is the same person existing in dozens of apps, each with its own idea of who they are. On a server, one plugin covers in-game permissions, which makes the whole thing much easier to reason about.
Nobody reviews access either. No auditor is going to ask you to prove who had mod in Q3. I'd still do it, because a monthly "who still needs this?" check takes a few minutes: run /lp log userhistory on each staff member to see what access they've been given, and ask whether they're still around and still moderating. It's the same idea as a quarterly access review at a small company starting on IAM, with less paperwork.
The biggest difference is that trust is social. Your mods are your friends. At work, a leaver is a process: HR sets a date and the access goes. On a server, taking mod away from a friend who's drifted off is awkward, and the easy thing is to leave it. That's how you end up with five mods, two of whom haven't logged in since last summer. A track helps, because demote feels like a normal step and less like a punishment. Temporary group membership helps even more, since the access expires and nobody has to have the conversation.
The blast radius is smaller too. The worst case on a Minecraft server is usually a griefed world and a restore from backup, but a compromised server can mean a compromised host.
Useful links
- Why LuckPerms? (LuckPerms wiki)
- Advanced setup (LuckPerms wiki)
- Command usage (LuckPerms wiki)
- Log commands (LuckPerms wiki)
- LuckPerms default config.yml (GitHub)
- Permission level (Minecraft Wiki)
- What are access reviews? (Microsoft Learn)
- What is Privileged Identity Management? (Microsoft Learn)
- What is Conditional Access? (Microsoft Learn)
- Log4Shell (CVE-2021-44228), the Minecraft-chat exploit (Tenable)
Top comments (0)