How to Make Yourself (and Staff) Admin on Rust Console: OwnerID vs AdminID vs ModeratorID

How admin actually works on Rust Console

First, clear up the biggest misconception. There is nothing to install and no add-on that hands out ranks. On console, admin power comes from three built-in role commands that live on the server itself, so ignore any guide that points you at extra software to set up permissions.

You cannot just type these commands in game. You run them one of two ways: through your host's control panel, or over WebRCON using a bot connected to your server. Once your gamertag holds a role you also get an in-game admin menu, but the assignment itself has to come from the panel or the bot first.

OwnerID vs AdminID vs ModeratorID: what each role can do

Rust Console has three admin tiers, and they stack from lowest to highest: Moderator, then Admin, then Owner. Each one is granted to a specific gamertag.

ModeratorID is your day-to-day policing role. Moderators can kick, ban, mute, teleport and deal with rule-breakers, but they are kept away from the settings that change how your server runs. This is the role you hand to a new or trial staff member.

AdminID sits above that. An Admin gets the fuller in-game toolset and more trust, which fits a senior staff member who runs events and helps you manage the server day to day.

OwnerID is the top of the tree. An Owner can do everything, including assigning and removing other people's roles. Treat Owner as the keys to the whole building and give it out sparingly.

Here is the rule that catches people out: one gamertag holds one role at a time. You do not stack them, and you do not need to. Owner already outranks Admin and Moderator, so adding yourself as Owner and then also as Admin does nothing useful and can leave you unsure which role is actually active.

Step 1: make yourself Owner (the bootstrap you cannot skip)

There is a chicken-and-egg problem here. To run ownerid on your own gamertag, you need access to run commands. But you have no access yet. So the very first Owner is always set outside the game, through your host.

If you rent from G-Portal, you set your owner gamertag in the server configuration or run the command from the panel's RCON console. G-Portal connects to a bot as direct WebRCON, meaning you use the server IP, the RCON port and the RCON password. If you would rather manage this from a clean dashboard, a G-Portal Rust Console bot connects over that same WebRCON channel and lets you set roles with a button instead of typing raw commands.

On Nitrado the setup is even simpler, because it links to a bot with a one-click account connection, so there is no IP or password to copy across. Either way, the first command you run is the same: ownerid "YourGamertag".

Then disconnect from the server and rejoin. Your Owner powers only appear after you reconnect.

The exact commands, and the quotes gotcha that breaks them

Once you have Owner, promoting anyone else is three short commands. Swap in the exact gamertag each time: ownerid "gamertag" for full control, adminid "gamertag" for an admin, and moderatorid "gamertag" for a moderator.

The single most common reason a command fails is the gamertag itself. Xbox gamertags can contain spaces, and any gamertag with a space must be wrapped in quotation marks, or the server reads only the first word and misses the rest. Quote every gamertag to be safe, and match the spelling and capitalisation exactly, because the server does not guess. Copy it straight from the player list rather than typing it from memory.

And say it one more time: whoever you just promoted has to fully leave the server and rejoin. A role never applies to someone who is already connected. Nine times out of ten, the command that did not work is really the person who did not reconnect.

Role assignments save to your server's own user list, so they survive restarts and wipes. If you want to be thorough, run server.writecfg after making changes to lock everything to the config. That matters more for gameplay settings, which are convars that reset on restart unless you write them, but it is a good habit for roles too.

Rust Console admin commands not working? Run this checklist

If a role still is not sticking, work through this in order. It is almost always one of these.

They did not reconnect. The fix is a full disconnect and rejoin, not a respawn. This is the number-one cause by a mile.

The gamertag was wrong. A typo, missing quotes around a name with a space, or the wrong capitalisation will all fail silently with no error to warn you.

You stacked roles on one gamertag. If you already made yourself Owner, a later adminid or moderatorid on the same gamertag will not give you a lower role, because Owner outranks both. Pick one role per person.

Your bot or tool is not actually on RCON. If players can join the server but your bot cannot connect, you almost certainly put the game port where the RCON port belongs. The game port is 28015 over UDP, while WebRCON usually listens on 28016 over TCP. They are different numbers for different jobs, and this catches nearly everyone. Our breakdown of the RCON port versus the game port walks through it.

RCON is not enabled. Some host setups need rcon.web set to 1 before WebRCON will accept a connection at all.

Auth is failing on the password. A host-generated RCON password with special characters or spaces can break the login, and Rust briefly locks out RCON after repeated failed attempts, so hammering retries only makes it worse. Slow down and fix the password first. If you are seeing an RCON authentication failed message, that guide has the exact fix.

Give a friend or staff admin without handing over the keys

When you promote your own people, match the role to the trust level. A brand-new helper or a friend you are trialling gets moderatorid, which lets them police chat and deal with cheaters but keeps them out of your settings. A proven senior gets adminid. Owner stays with you and, at most, one co-owner you would trust with your bank card, because every Owner can remove every other Owner, including you.

Run the command, have them fully leave and rejoin, and they are in. When someone leaves your team, revoke their access straight away with the matching remove command: removeowner, removeadmin or removemoderator, followed by the gamertag in quotes. Rotate roles the moment staff change, the same way you would change a lock.

Let a bot handle roles and permissions the clean way

Typing raw commands is fine when it is just you and one friend. Once you have a real staff team, running everything by hand gets risky. There is no record of who did what, nothing stops a moderator firing off a command they should not, and a mistyped ban can go unnoticed for days.

This is where a proper bot earns its place. Vantic signs your staff in with Discord only, so there are no passwords to share or leak, and it maps your Discord roles to in-game roles, so a promotion in your server is a promotion in the game. You set per-role command permissions, so a moderator simply cannot run owner-level commands, and every action lands in an audit log. Roles, tickets and per-role permissions live in one place, and revoking someone is a single click instead of a command you have to remember. Nobody on your team ever touches a raw RCON line.

Frequently asked questions

Keep reading

connect a bot to G-Portal · find your WebRCON IP, port and password · RCON port vs server port · tickets and role permissions · the best Rust Console bot