How to Assign Admin Rights on a Project Zomboid Server Print

This guide will show you how to assign Admin Rights on a Project Zomboid Server

Click here to order your Project Zomboid server with AA Game Hosting.

Assigning admin rights on your Project Zomboid server is one of the first steps toward keeping your world running smoothly. Whether you’re hosting a small co‑op session with friends or managing a large public server, having at least one trusted admin ensures you can moderate players, adjust settings on the fly, and handle unexpected issues without restarting the entire server. In this guide, you’ll learn exactly how to grant admin privileges quickly and safely, so you can focus on shaping the apocalypse, not wrestling with server commands.

Adding an Admin to Your Project Zomboid Server

Admin-level access grants your account different levels of access, with the ability to execute Admin commands in-game, such as kick, ban, mute, teleport, and many more. Here's how you become one.

There are currently five (5) admin levels available, each offering its own set of commands and abilities. 

• admin
• moderator
• overseer
• gm
• observer

We will be using the "admin" level for this guide, which has the highest level of access. If you read further below, there is a section where you see an in-depth description of each of their level of access.

Adding an Admin Using the Console

These are the steps to give a player Admin Access:

1. Make sure the server has started. To do that, navigate to your Game Panel (You can click this link for easy access).

You will see if your game server is running or not. Click on the "Start" button if it isn't running.

2. Next, navigate to the Web Console section on the left-hand side panel.

3. Enter the command SetAccessLevel username level. Replace username with your username and level with the selected admin level, then press Enter.

You have now added an Admin account to your Project Zomboid server.

4. To remove any access level of any accounts you've set as admin, use none as the level: SetAccessLevel username none

According to the developers, below is the detailed description of the various admin levels and their commands (please note that this list is subject to change):

Observer:

•   Toggle god mod (on himself only)
•   Toggle invisible (on himself only)
•   See players connected (/players)
•   Teleport to a player (can't teleport a player elsewhere)
•   Can toggle noclip (on himself only)
•   Teleport to coordinates
•   See server options
•   Can open locked doors
•   Can go inside safehouses
•   Can't be kicked if too laggy
•   Can always join the server (even if full)
•   Can talk even being invisible
•   Sees invisible players
•   Can't be hit by players
•   Log is directly invisible/invincible
•   Can see players' stats (name, skill, traits...) with a click on player -> Check Stats (but can't modify them)

GM:

•   Everything an Observer can use, plus:
•   Toggle god mod (on himself and others)
•   Toggle invisible (on himself and others)
•   Can toggle noclip (on himself and others)
•   Teleport a player to another player  
•   Use /alarm, /gunshot, /thunder and /chopper
•   Start/Stop rain
•   Add item
•   Add xp

Overseer:

•   Everything a GM can use, plus:
•   Create horde
•   Kick user
•   Display server message
•   See the connection info of a player
•   Disconnect a player by connection number (/disconnect)
•   Use /nightlengthmodifier
•   Can modify player stats in the player stats UI
•   Can ban a player from /all chat

Moderator:

•   Everything an Overseer can use, plus:
•   Ban/Unban user (including steam ID)
•   Manipulate whitelist (/adduser, /addusertowhitelist, /addalltowhitelist, /removeuserfromwhitelist
•   Change access level (can't set admin)
•   Can set up safehouses

Admin:

•   Everything a Moderator can use, plus:
•   Save world
•   Quit world
•   Change access level (including admin)
•   Reload server options
•   Change server options
•   Send pulse
•   Reload Lua files
•   Bypass the Lua checksum