How to Manage Your Minecraft Server (OP, Whitelist, Ban)

Guide Java Bedrock

Quick answer: From the server console or as an operator: /op Name gives admin powers, /whitelist on plus /whitelist add Name locks the server to friends only, /ban Name and /kick Name remove troublemakers. All free, built into the game.

What you need

Your own server (or the owner's console access)
Player usernames exactly as written
No downloads - everything is built in

Step by step

OP (operator): run op PlayerName in the server console, or /op PlayerName as an existing operator. Ops can use every command - give it only to people you trust.
Remove powers with /deop PlayerName.
Whitelist: /whitelist on locks the server to an invite list. Add friends with /whitelist add PlayerName, remove with /whitelist remove, and check with /whitelist list.
Kick vs ban: /kick Name disconnects them once; /ban Name blocks rejoining permanently. /pardon Name unbans.
Operators have permission levels (1-4) set in server.properties (op-permission-level) - level 4 controls the server itself.
All these settings live as files too: ops.json, whitelist.json and banned-players.json next to the server jar - edit with the server stopped.
Aternos and other hosts expose the same commands in their web console - no file editing needed.

Java vs Bedrock

Realms instead of a self-hosted server? The Realms menu has invite and permission buttons - no commands needed.

Versions: These commands have been stable for years and work on every current Java server version. Bedrock dedicated servers use the same commands.

Frequently asked questions

Should I use a whitelist?

Yes, always, for a friends-only server. It is the single most effective protection - nobody outside the list can even connect.

Can an op ban the owner?

From in-game commands, level-4 ops can do almost everything. Only the console (you) outranks them - choose ops carefully.