Skip to content

Enshrouded 1.0 is out! 🎉 Get 25% OFF your next Enshrouded Server today!

RustMods & Plugins

Use the Permissions Manager Plugin on Rust

Install Permissions Manager by hand and use its in-game /perms menu to grant and revoke Oxide permissions and groups.

Updated 4 min read

Permissions Manager gives a Rust server an in-game screen for permissions. Instead of typing a grant command into the Console for every player, an admin opens a menu, picks a player or a group, and switches permissions on and off. This guide covers installing it, opening it, and the settings behind it.

Checked against Permissions Manager 2.1.2 by Steenamaroo, updated July 2026 on its Codefling page, October 2026. That page marks it as compatible with both Oxide and Carbon.

Where to get it

Permissions Manager is listed on Codefling, not on uMod. The Plugins tab searches uMod, so a search there won't find it. You install it by hand:

  1. Download the plugin from its Codefling page.
  2. On your Rust server, open the File Manager and go to oxide/plugins (on Carbon, carbon/plugins).
  3. Upload the file there and keep its file name as downloaded.
  4. On Oxide, a plugin added to a running server stays unloaded until you Restart the server or type oxide.load <Name> in the Console, where <Name> is the name of the file you uploaded. On Carbon it loads by itself. The Console prints a Loaded plugin line when it works, and the plugin shows under Installed on the Plugins tab.

The server needs Oxide or Carbon first. How to install Oxide/uMod plugins on your Rust server covers that, and how an uploaded plugin shows in the Installed list.

Who can open it

The plugin registers one permission, permissionsmanager.allowed. The page says the plugin works for anyone holding that permission, or for any admin at auth level 2, which is a server owner. Give it to a trusted moderator from the Console:

oxide.grant user 76561198000000001 permissionsmanager.allowed

On Carbon, use c.grant user 76561198000000001 permissionsmanager.allowed instead. The oxide.grant form prints nothing there.

Replace the number with the player's SteamID64. A permission only exists once its plugin has loaded, so do this after the plugin is running.

Open the menu

All of these are chat commands, typed in game:

CommandWhat it opens
/perms or /perms playerA list of players, so you can pick one
/perms groupA list of groups
/perms player <playername>The permissions screen for that player
/perms group <groupname>The permissions screen for that group

The page lists what it does: assign permissions to players (online or sleeping) and to groups, add or remove a player from groups, and remove every player from a group in one click with Remove All. It says it supports unlimited plugins, permissions and groups, shown a page at a time.

Back up your permissions

/perms data is the command for backing up and restoring permissions, groups or both, to a local data file or to SQL. The page warns about the difference: saving to SQL adds to what was already saved, while saving to the local data file overwrites the previous backup with what the server has now. Back up before a big reshuffle.

To empty a group in one go, the plugin has a Remove All button on a group's screen, and a console command, EmptyGroup <groupname>.

Settings

The first load writes a config file named after the plugin to oxide/config (carbon/configs on Carbon). The page lists these options: the colours of the chat title, chat message, GUI label and the on and off buttons; AllPerPage, which makes the All and None options work per page rather than per plugin; the GUI transparency from 0 to 1; and a plugin block list, written in lower case and separated by commas with no spaces, which hides those plugins from the menu.

Common problems

  1. Nothing happens on /perms. You need permissionsmanager.allowed, or admin level 2.
  2. A permission shows as "Inherited" and won't revoke. The player is in a group that has the permission. Revoke it from the group, or take the player out of the group.
  3. A player was removed from a group but still has a permission. They were given that permission directly at some point. Revoke it from the player.

Ready to launch your Rust server?

Aussie hardware, NVMe disks and DDoS protection, with the version and mod loader yours to change whenever you like.

See Rust plans