Rust Admin Plugins 2026: uMod Tools and Staff Permissions

Published on | Updated

The Rust admin plugins worth installing in 2026, with each plugin's chat command and Oxide permission, plus the exact commands to give moderators a group.

The Rust logo in front of a radar dish and pine trees

You want staff who can check a cheat report and mute a spammer without getting the keys to the whole server. Which Rust admin plugins do that, which command starts each one, and which permission does a moderator need? The answers below come from the plugins' own source files and uMod's plugin data (checked 4 November 2026), and from the Oxide.Rust source for the permission commands.

Quick answer: Install five admin plugins first: Vanish (/vanish, permission vanish.allow) to watch players unseen, Admin Radar (/radar, adminradar.allowed) for an on-screen radar of players and entities, Player Administration (/padmin, playeradministration.access.show plus one permission per action) for kicks, bans and mutes from a menu, Admin Hammer (/ah, adminhammer.allow) to see who owns a base, and Admin Logger to record what staff do. Give staff an Oxide group instead of ownerid: oxide.group add mod, oxide.usergroup add <SteamID64> mod, then oxide.grant group mod <permission> for each tool. All of them are direct downloads on uMod.

The Rust admin plugins worth installing

Versions and dates are from uMod's plugin data on 4 November 2026; commands and permissions are from each plugin's .cs file.

Plugin (author)Version, releasedWhat it doesChat commandPermissions to give staff
Vanish (Whispers88)2.1.5, 6 Aug 2026Makes you invisible to players and NPCs/vanish, /invvanish.allow, vanish.invviewer, vanish.unlock, vanish.teleport, vanish.damage, vanish.permanent
Admin Radar (nivex)5.4.4, 2 Oct 2026Radar "to help detect cheaters and other entities"/radar, /radar listadminradar.allowed, adminradar.auto, adminradar.list
Player Administration (ThibmoRozier)1.6.10, 7 Aug 2026Menu to kick, ban, mute, freeze, spectate, teleport and heal/padminplayeradministration.access.show plus .access.kick, .access.ban, .access.mute, .access.spectate, .access.teleport and more
Admin Logger (1AK1)2.4.2, 4 Jun 2026Logs admin commands to a file, the console and optionally Discordnonenone
Admin Hammer (mvrb)1.13.1, 10 Nov 2025Shows owner, authorized players, box contents and lock codes of what you hit/ahadminhammer.allow
Godmode (dFxPhoeniX)4.2.16, 15 Sep 2026Makes you invulnerable/god, /godsgodmode.toggle, godmode.invulnerable, godmode.admin
NTeleportation (nivex)1.9.6, 6 Aug 2026Admin teleports, plus homes and teleport requests for players/tp, /tpn, /tpbnteleportation.tp, nteleportation.tpn, nteleportation.tpb
Remover Tool (Tryhard)4.3.48, 3 Sep 2026Removes entities, in admin mode regardless of owner/remove adminremovertool.admin, removertool.structure, removertool.all
Copy Paste (misticos)4.3.0, 3 Sep 2026Saves and pastes buildings/copy, /paste, /undocopypaste.copy, copypaste.paste, copypaste.undo

By uMod's download counter, Vanish leads with 548.9K downloads, followed by NTeleportation (470.5K), Admin Radar (455.0K), Remover Tool (451.9K) and Copy Paste (438.5K). Admin Utilities and Admin Panel also sit in the top five of uMod's "admin" search; we did not review their code here.

Install the plugins first

A permission only exists once its plugin is loaded, so install before you grant. Download the .cs file from the plugin's uMod page and put it in oxide/plugins. On our Rust server hosting plans Oxide/uMod is supported on every plan, and you upload plugins with the panel's file manager or over SFTP. Oxide's plugin watcher is on by default, so a new or changed file loads without a restart. Most plugins write their settings to oxide/config/<PluginName>.json; after an edit, run oxide.reload <PluginName>. Our uMod install guide has the full walkthrough.

Set up a mod group step by step

Rust has two admin layers, and mixing them up causes most staff problems:

  1. Rust's own auth: ownerid <SteamID64> "name" or moderatorid <SteamID64> "name" in the server console. Facepunch's server guide says the player must reconnect to get the auth level; the entries are saved in users.cfg in server/<identity>/cfg/.
  2. Oxide permissions: groups and permissions that plugins check. Oxide puts every player in the default group on connect and adds players with auth level 2 (owners) to the admin group. The plugins above read these permissions, so moderators do not need moderatorid.

Run the commands below in the server console or over RCON. In game, players added with ownerid can also run them from the F1 console.

oxide.group add mod
oxide.usergroup add 76561198123456789 mod
oxide.grant group mod vanish.allow
oxide.grant group mod adminradar.allowed
oxide.grant group mod playeradministration.access.show
oxide.grant group mod playeradministration.access.kick
oxide.grant group mod playeradministration.access.mute
oxide.grant group mod playeradministration.access.spectate
oxide.grant group mod nteleportation.tp

For senior staff, make mod the parent group. Oxide checks a group's parent when it looks up a permission, so senior gets everything mod has plus its own extras:

oxide.group add senior
oxide.group parent senior mod
oxide.grant group senior playeradministration.access.ban
oxide.grant group senior adminhammer.allow
oxide.grant group senior adminradar.list
oxide.grant group senior godmode.toggle
oxide.grant group senior godmode.invulnerable

Then protect the owners: with these, Player Administration refuses to ban, kick, kill, hurt or reset anyone in the admin group.

oxide.grant group admin playeradministration.protect.ban
oxide.grant group admin playeradministration.protect.kick
oxide.grant group admin playeradministration.protect.kill
oxide.grant group admin playeradministration.protect.hurt
oxide.grant group admin playeradministration.protect.reset

Check the result with oxide.show group mod, oxide.show user <SteamID64> or oxide.show perm vanish.allow (every player and group with that permission). Remove someone with oxide.usergroup remove <SteamID64> mod. VIP and player groups are in our Oxide permissions guide.

Messages you will see

MessageWhat it meansFix
Permission 'vanish.allow' doesn't existThe plugin is not loaded, or a typoCheck oxide.plugins, then grant again
Group 'mod' doesn't existThe group was never createdoxide.group add mod
Multiple players were found, please specify: ...The name matches more than one playerUse the SteamID64
Player 'name' not foundUnknown name and not a valid IDUse the SteamID64 (17 digits or more)
You do not have permission to use the command 'oxide.grant'!Run in game without ownerid or the oxide.grant permissionUse the server console or RCON

Four traps in the permission system

  • Wildcards are a snapshot. oxide.grant group admin playeradministration.protect.* adds the matching permissions registered at that moment. A permission added by a later plugin version is not included, so repeat wildcard grants after updates.
  • Never give staff oxide.grant, oxide.group or oxide.usergroup. Anyone with those permissions can run the commands, and grant accepts any registered permission, including yours.
  • moderatorid is not neutral. Admin Radar gives the radar to everyone with auth level 1 or higher by default ("Restrict Access To Auth Level": 1), and NTeleportation opens its admin teleports to moderators and admins ("Usable By Moderators" and "Usable By Admins": true). Change those if Oxide groups should decide.
  • Removing ownerid does not remove Oxide admin. Oxide adds owners to admin on connect and never takes them out. After removeowner, also run oxide.usergroup remove <SteamID64> admin.

Plugin notes and config gotchas

From the source code, and the cause of most "the permission does not work" reports.

Vanish

  • /vanish checks vanish.allow. Two auto-vanish settings in the config mention "the vanish.use perm", but no vanish.use permission exists.
  • vanish.permanent vanishes the player on every connect and plugin load, and /vanish then only answers "You are in a permanent vanish mode". Do not give it to staff who need to reappear.
  • vanish.damage does nothing until "Use OnEntityTakeDamage hook" is true (default false, "for better performance"). With the hook on, a vanished player without vanish.damage deals no damage and other players cannot hurt them.
  • vanish.unlock opens locked doors and boxes while vanished. vanish.teleport moves you to a map marker you place while holding the reload key, after you set "Enable teleport to marker when vanished" to true.
  • /inv (needs vanish.invviewer) opens the inventory of the player you look at within 5 metres, or of a name or SteamID you add.
  • By default Vanish runs the noclip command when you vanish, pauses metabolism and fly hack detection, skips antihack violations and plays the vanish sound only for you.

Admin Radar

  • If "Restrict Access To Steam64 IDs" has any entry, only those IDs get the radar, even with adminradar.allowed.
  • adminradar.auto starts the radar when you wake up; /radar list (with adminradar.list) shows who has one running.

Player Administration

  • "Use Permission System" is true by default, so every button needs its own .access permission on top of .access.show. Set it to false and .access.show alone opens every action.
  • Muting is one permission, playeradministration.access.mute, for chat and voice; since 1.5.19 the plugin moves old .access.chatmute and .access.voicemute grants to it.
  • The freeze button runs the freeze command of the separate Freeze plugin.
  • Every kick and ban from the menu is announced in chat (Player {0} has been banned: {1}). The config has "Broadcast Kicks" and "Broadcast Bans" switches, but version 1.6.10 never reads them, so false does not silence it.

Godmode

  • /god needs godmode.toggle, but damage is only blocked with godmode.invulnerable as well. Give both, or godmode switches on and the player still takes damage.
  • /god <player> and /gods need godmode.admin. Gods get a visible "[God] " name prefix by default.

Admin Hammer

  • /ah toggles it; then look at an entity and right-click while holding a hammer.
  • In 1.13.1 the "ShowCode" setting is only used in a commented-out line, so code lock codes still show in chat when you hit a locked door or box. Give adminhammer.allow only to people you trust with every code on the server.
  • After a tool cupboard or box it runs the chat command /box ("CommandToRun"); leave that blank if no plugin of yours uses /box. Its last release (10 November 2025) is the oldest here, so test it after every Rust update.

NTeleportation and Remover Tool

  • /tp "player" takes you to a player, /tp "player" "targetplayer" moves one player to another, /tp x y z goes to coordinates, /tpn puts you behind a player and /tpb takes you back. nteleportation.admin is not the /tp permission; it covers /tphome and setting locations such as town.
  • /remove admin stays on for 300 seconds by default, and hitting a connected player with it kicks that player. Copy Paste is covered with Kits in our essential plugins list.

Logging: who did what

  • Admin Logger writes to the console and oxide/logs/AdminLogger/adminlogger_adminlog-<date>.txt. It logs /vanish, /radar and opening /padmin for anyone with that plugin's permission. Rust console commands (kick, ban, mute, teleport, give, spawn) and Player Administration's buttons are only logged when the sender has a Rust auth level from ownerid or moderatorid. Fill in "Discord Messages webhook" to copy the lines to Discord.
  • Player Administration logs every ban, kick, mute, freeze, inventory view and reset with the staff member's name in oxide/logs/PlayerAdministration/, whatever their auth level.
  • Admin Hammer prints a console line per use: who, which entity, its owner and the position.
  • Spot checks: /radar list, /gods and oxide.show perm <permission>.

So a moderator with only Oxide permissions is missing from Admin Logger's console-command log, but their bans and kicks still land in Player Administration's log. RCON apps are in our Rust RCON guide.

Community or Modded listing

Oxide's config (oxide/oxide.config.json) has a "Modded" option, true by default. Set it to false and Oxide warns at startup: "The server is currently listed under Community. Please be aware that Facepunch only allows admin tools (that do not affect gameplay) under the Community section". To stay under Community, judge each plugin by that line.

After a Rust update or the monthly wipe

Facepunch's community server guidelines warn that game updates "could have an impact on Servers and other software (in the worst case making them inoperable)". Oxide.Rust 2.0.7839 (22 October 2026) was the current build when we checked. Update Oxide first, then the plugins, and test /vanish, /radar and /padmin before you open the server. Our plugin update and wipe guide has the full order.

Leaked plugins

"Leaked" plugins are paid plugins re-uploaded without the author's permission. Staff tools do not need them: all nine plugins above are direct downloads on uMod, six under the MIT license and Admin Radar under GPL-3. A leaked copy gets no updates from its author, which hurts most on update night, and Oxide compiles and runs every .cs file in oxide/plugins, so it is code from an unknown uploader running on your server. Facepunch's guidelines make owners responsible for "ensuring your Servers are free from viruses, malware and spyware". Buy paid plugins from the author's own store page.

FAQ

What admin plugins do most Rust servers use?

uMod publishes downloads, not server counts. On 4 November 2026 Vanish had 548.9K downloads, NTeleportation 470.5K, Admin Radar 455.0K, Remover Tool 451.9K, Copy Paste 438.5K and Player Administration 230.1K. For moderation, Vanish, Admin Radar, Player Administration, Admin Hammer and Admin Logger cover watching, finding, punishing, ownership checks and records.

How do I give someone admin on my Rust server with Oxide?

ownerid <SteamID64> "name" gives full Rust owner rights after a reconnect, and Oxide then adds that player to its admin group. For staff, create a group (oxide.group add mod), add them with oxide.usergroup add <SteamID64> mod and grant only the permissions they need.

Can players see a vanished admin?

Not in the world. Vanish stops the server sending your player to other players, makes NPCs ignore you and turns off your collider. You are still connected, so you still count toward the player number. Godmode's "[God] " prefix is a different plugin and is visible.

Why does my moderator get "You do not have permission to do this"?

That is Vanish's reply without vanish.allow. Run oxide.show user <SteamID64>: either the player is not in the group, or the grant never happened because the permission name was wrong, such as vanish.use (Oxide then answers "Permission 'vanish.use' doesn't exist"). In Player Administration, every button needs its own .access permission.

Are leaked Rust plugins safe?

You cannot check where a leaked file came from or what was changed, it gets no updates from the author, and Oxide runs it with everything else on your server. The admin plugins in this guide are direct downloads on uMod, so there is no reason to look for leaked copies.

Do these admin plugins work on Carbon?

We only checked them against Oxide's source. Carbon is a separate framework (Carbon vs Oxide), so check each plugin's page and Carbon's documentation first. Our Rust plans are set up for Oxide; Carbon support on them is not confirmed.

Sources

All opened on 4 November 2026: