Owner vs Admin vs Moderator on Rust Console: Which Role Can Do What

The three authority tiers, and who each one is for

Rust Console gives you three staff levels, each assigned by gamertag: Owner, Admin, and Moderator. Think of them as a ladder. Owner sits at the top with full control, Admin gets the heavy in-game tools, and Moderator gets the day-to-day policing tools. A gamertag holds exactly one of these at a time, which matters more than it sounds and comes up again later.

Owner (the ownerid tier) is you and anyone you trust with the keys to the whole server. Owners have everything an admin has, and they sit above every other tier, so an admin or moderator cannot kick or ban them. Keep this list tiny. On most servers it is just the person paying the host bill.

Admin (the adminid tier) is for staff who need to build, test, and step into fights. These are the people you trust to spawn an event, ban a cheater, or fly through a base to check for exploits.

Moderator (the moderatorid tier) is your front line. These are the helpers who watch chat, respond to reports, and spectate anyone who looks suspicious. They get a deliberately lighter toolset so a new volunteer cannot accidentally, or deliberately, wreck a wipe.

What each role can actually do in game

The difference between the tiers is not just a label. It changes which commands the game will let that person run.

Admins and Owners get the powerful stuff. NoClip lets them fly through walls and terrain to inspect a base or catch a cheater mid-exploit. God mode makes them invincible, which is essential when you are testing or breaking up a spawn-camp without dying yourself. They can lock the map to eternal daylight and control the time of day, spawn events over RCON like event_helicopter, event_airdrop, event_cargoheli and event_cargoship, ban with banid (id, reason, duration), teleport with teleportpos, and check any player's location with printpos.

Moderators get the policing toolset, not the god toolset. A moderator can spectate a player to quietly watch a suspected cheater without being seen, and teleport to a gamertag to respond to a report on the spot. What they do not get is NoClip or God mode. That gap is the whole point: your helpers can gather evidence and answer reports without holding the tools that could ruin the map. When a spectate confirms someone is cheating, the moderator flags it to an admin or owner, who has banid to remove them. If a specific moderator keeps earning that trust, you promote them to Admin rather than bolting extra powers onto the mod role.

How to add a moderator or admin over WebRCON

First, forget everything you have read about the PC version. There is no F1 developer console on Rust Console, and there are no plugins to install. You assign roles by sending the command over WebRCON, either through your host's panel or through a bot connected to your server.

WebRCON connects with three things: your server IP, the RCON port, and the RCON password. The RCON port is a separate TCP/WebSocket port (commonly 28016) and is not the same as the game port your players join on (28015). Mixing those two up is the number one reason a first connection fails, so if you are not connected yet, sort out the RCON port versus the game port before you try to run anything.

Once you are connected, the commands are short:

1. Add a moderator: moderatorid "GamerTag Here"

2. Add an admin: adminid "GamerTag Here"

3. Add an owner: ownerid "GamerTag Here"

Two details make or break this. Quotes: any gamertag with a space in it must be wrapped in double quotes, or the command reads only the first word and assigns the wrong person, or nobody at all. Get in the habit of quoting every gamertag, even single-word ones. Reconnect: the new role does not apply while the player is already in the server. They have to leave and rejoin for the tier to load. If you just promoted someone and they say nothing changed, tell them to reconnect before you start troubleshooting. If the person you are setting up is yourself, follow the same steps to make yourself admin on Rust Console.

Why making yourself Owner can block another role

Here is the trap that catches new owners. Because a gamertag can only hold one tier at a time, stacking roles on your own gamertag does not add power, it creates a conflict.

Say you added yourself as a Moderator on day one to test things, then later ran ownerid on the same gamertag to take full control. Those two entries now fight each other, and you can end up with the wrong effective permissions, or none at all. People assume more roles means more access. On Rust Console it is the opposite: the system expects one clean assignment per gamertag.

The fix is simple. Pick one role per gamertag, and for yourself that role is always Owner, because Owner already sits above Admin and Moderator. Remove any lower entry for your own tag first, then add ownerid. You never need to also be an admin or a mod on your own server. The same rule applies to your staff: promote a moderator to admin by removing the moderator entry and adding the admin entry, not by piling both on.

Removing a role, and why role sync matters

Access you grant does not expire on its own. To revoke a role you run the matching remove command over WebRCON: removeowner "tag", removeadmin "tag", or removemoderator "tag". As with adding, quote gamertags that contain a space, and the person may need to reconnect before the removal fully bites.

This is exactly where turnover burns owners. A moderator quits your Discord, stops showing up, maybe even falls out with the community, and still has spectate and teleport in game because nobody remembered to run removemoderator. Every departed staff member you forget is a live set of keys floating around. On a manual setup, staying clean means keeping a list and running the right remove command every single time someone leaves.

That is the argument for role sync. When your in-game tiers are tied to your Discord staff roles, promoting or removing someone in Discord updates their server access automatically, with no forgotten remove command. Vantic keeps Discord roles and in-game Owner, Admin, and Moderator tiers in sync both ways, so a staff member who loses their Discord role loses their in-game powers at the same moment. It pairs naturally with per-role command permissions in your ticket system, so the same role that decides who can claim and close support tickets also decides who holds NoClip. Set the roles once, and staff access stays honest as your team changes.

Do role assignments survive a restart?

Mostly yes, and this is one place Rust Console is kinder than owners expect. Live convars like gather scale, decay, and your PvP toggles reset on reboot unless you write them to config, but Owner, Admin, and Moderator entries are stored in the server's user list, not held in memory like a convar. That list is built to survive restarts, including the automatic reboots G-Portal performs when Facepunch ships a patch, so your admin roster does not vanish every time the server bounces.

To be safe, run server.writecfg once after you finish setting up or changing staff. That writes the current list to disk so a reboot cannot catch it unsaved. If you ever find a freshly assigned role not sticking after a restart, that same command is the fix, and the exact symptom is covered in more depth in why admin commands are not sticking after a restart. For everyday role assignment, add the tier, have the player reconnect, and it stays put.

Frequently asked questions

Keep reading

tickets and per-role command permissions · How to make yourself admin on Rust Console · Rust Console admin commands over RCON cheat sheet · Fixing admin commands that do not stick after a restart · the full Rust Console bot command list