Game Server Admin Roles and Permissions Explained (Owner, Admin, Mod)

Most game servers have at least two levels of power: full admins who can change anything, and everyone else. Many add more: moderators who can kick and ban but not spawn items, or numbered permission levels. The safe rule is least privilege: only the owner holds the master password and server files, a small number of trusted admins get full rights, and moderators get only the commands they need. How you set this up depends on the game: some use a list of Steam IDs, some an admin password, some numbered levels or a plugin with groups.

The usual roles

Owners and admins can break the world by accident. Moderators can only annoy people. Keep that difference in mind when someone asks for "admin to help out".

How the main games handle it

Minecraft: Java Edition

Vanilla uses operator levels 1 to 4, stored in ops.json:

/op <name> grants the default level from op-permission-level in server.properties (4 by default). Edit ops.json to give a lower level. For anything finer, Paper and Spigot servers use a permissions plugin like LuckPerms, which lets you build groups such as moderator with exactly the commands you choose.

Rust

Rust has two built in levels, set by Steam ID in the console:

• ownerid <steamid> "name" gives full admin.
• moderatorid <steamid> "name" gives moderator, which can use most admin commands but cannot add or remove other owners or moderators.

Run server.writecfg afterwards so the change is saved to users.cfg. For finer control, Oxide and Carbon have permission groups (oxide.group add mods, oxide.grant group mods <permission>). Our guide on how to make yourself admin on a Rust server walks through the basics.

Valheim

Valheim keeps it simple: add Steam IDs (or platform IDs for crossplay players) to adminlist.txt in the save folder. Admins can kick, ban and use the server's devcommands. There are no lower levels without mods. bannedlist.txt and permittedlist.txt sit next to it. See Valheim admin commands.

ARK: Survival Ascended

Anyone who knows ServerAdminPassword can type enablecheats <password> and become admin. To skip sharing the password, list Steam or Epic IDs in AllowedCheaterAccountIDs.txt (in ShooterGame/Saved) so they are admin on join. There are no lower built in roles. See ARK: Survival Ascended admin commands.

Project Zomboid

Project Zomboid has real built in roles: admin, moderator, overseer, GM and observer. Set them with /setaccesslevel "username" moderator. Each level has a fixed set of rights, and moderators cannot change server settings. Details in Project Zomboid admin commands.

7 Days to Die

7 Days to Die uses permission levels from 0 (highest) to 1000 (normal player) in serveradmin.xml. Admins get 0. You can then set each command's required level, so a level 1 moderator can kick but not spawn items. Use admin add <steamid> 0 in the console. See 7 Days to Die admin commands.

Source games and Garry's Mod

CS2, TF2 and Counter-Strike: Source use SourceMod's admin flags (admins_simple.ini), where each letter is a power: b generic, c kick, d ban, z root. Garry's Mod servers usually use ULX with groups like superadmin, admin and operator.

Setting up roles that hold up

1. One owner. Only the owner has the panel login, server files and RCON password. If you need a backup owner, choose one person and tell everyone who it is.
2. Grant by account ID, not shared passwords. Steam ID lists can be revoked per person. A shared admin password has to be changed for everyone whenever one person leaves.
3. Moderators get moderation, not cheats. Kick, ban, mute and teleport to a player cover most moderation.
4. Write the rules down. A short pinned post saying what each role can and cannot do prevents most staff arguments.
5. Log actions. Many games and plugins log admin commands. Read them now and then.
6. Remove access when people step back. Delete their IDs from admin files and rotate any shared password they knew.

If you also use RCON tools, give them a separate password from the in game admin password where the game allows it. See what is RCON.

Admins vs server access

Being admin in game is different from having access to the server itself. Panel, file and SFTP access lets someone edit configs, delete worlds and read passwords. Give it out even more carefully than in game admin.

Running staff on a hosted server

On a GamezServers server the owner keeps the panel login, while friends who split the bill each pay their share without needing access to your files. Admin lists like adminlist.txt or ops.json are edited in the file manager or over SFTP, and the live console lets you run admin commands directly.

FAQ

What is the difference between an admin and a moderator on a game server?

Admins can usually do everything, including spawning items and changing settings. Moderators can manage players (kick, ban, mute) but not change the world or server.

How do I give someone admin on my server without sharing the password?

Add their account ID to the game's admin list: adminlist.txt for Valheim, ownerid or moderatorid for Rust, ops.json for Minecraft, AllowedCheaterAccountIDs.txt for ARK.

Can I limit what an admin can do?

In games with levels or plugin permissions, yes: Minecraft with LuckPerms, Rust with Oxide or Carbon groups, 7 Days to Die levels, Project Zomboid access levels. Games like Valheim and ARK have only full admin unless you add mods.

How many admins should a server have?

As few as you can manage with. Two or three trusted admins and a few moderators cover most community servers.