Rust Server Permissions Guide – Oxide/Carbon

Which framework does your server run?Every command on this page changes to match.

Rust permissions, made simple

Permissions decide who can use each plugin feature on your server: who gets the VIP kit, who can teleport, who can use admin tools. Learn one command pattern and you can set up any plugin.

oxidecarbonFramework.grantWhat to dogroupGroup or userdefaultWhich onekits.kit.starterThe permission
grant / revoke: give or take away a permission.
group: everyone in a group gets it. user: just one player.
Permission names come from the plugin, usually pluginname.something.
Where to type these: your server console, RCON, or the in-game F1 console if you’re an owner (ownerid, auth level 2). Changes apply instantly. You don’t need to restart or reload anything.

Everyday commands

These cover almost everything you’ll do. The white parts are example values. Swap them for your own group, player or permission.

Give permissions

  • oxidecarbon.grant group vip kits.kit.vip

    Give a permission to every player in a group. This is the one you’ll use most.

  • oxidecarbon.grant user 76561198000000000 kits.kit.vip

    Give a permission to one player, by Steam ID or name. A Steam ID always finds the right player.

  • oxidecarbon.grant group default kits.kit.starter

    Give a permission to everyone on the server. All players are in default.

Take permissions away

  • oxidecarbon.revoke group vip kits.kit.vip

    Remove a permission from a group.

  • oxidecarbon.revoke user 76561198000000000 kits.kit.vip

    Remove a permission from one player. This only removes what you granted to them directly. See troubleshooting.

Create & manage groups

  • oxidecarbon.group add vip

    Create a new group. Use short, lowercase names with no spaces.

  • oxidecarbon.group add vip "VIP" 1

    Create a group with a display title and a rank. Both are optional. Some plugins show the title, and a higher rank means a more important group.

  • oxide.group set vip "VIP Member" 2

    Change an existing group’s title and rank.

  • carbon.group set vip title "VIP Member"

    Change an existing group’s title. Use rank instead of title to change its rank.

  • oxidecarbon.group parent vip_plus vip

    Make vip_plus inherit every permission vip has. How parents work.

  • oxidecarbon.group remove vip

    Delete a group. Its members stay on the server but lose the group’s permissions.

Add & remove players

  • oxidecarbon.usergroup add 76561198000000000 vip

    Put a player in a group. They get all of the group’s permissions immediately.

  • oxidecarbon.usergroup remove 76561198000000000 vip

    Take a player out of a group.

  • carbon.usergroup addall vip

    Carbon only. Add every known player to a group. Use removeall to empty it.

Check what’s set up

  • oxidecarbon.show user 76561198000000000

    List a player’s permissions and the groups they’re in.

  • oxidecarbon.show group vip

    List a group’s permissions and players.

  • oxidecarbon.show perm kits.kit.vip

    See every player and group that has a permission.

  • oxidecarbon.show groups

    List every group on the server.

  • oxidecarbon.show perms

    List every permission your loaded plugins register. Use it to find exact names.

Command builder

Pick what you want to do, fill in the blanks, then copy the command. It follows the framework you picked at the top.

Example: build a VIP group

Here’s a VIP group built from scratch. Next to each step, a panel shows what the group looks like after the command. The permissions are examples. Use the ones your own plugins list on their pages.

1

Create the group

Create the group with the title VIP and rank 1. It starts empty.

  • oxidecarbon.group add vip "VIP" 1
vipVIP · rank 1New group
PermissionsNone yet
PlayersNone yet
2

Add the perks

Grant the group each perk. Run one command per permission.

  • oxidecarbon.grant group vip kits.kit.vip
  • oxidecarbon.grant group vip backpacks.use
  • oxidecarbon.grant group vip quicksmelt.use
  • oxidecarbon.grant group vip skins.use
vipVIP · rank 14 perks added
Permissions
kits.kit.vipbackpacks.usequicksmelt.useskins.use
PlayersNone yet
3

Add your VIPs

Add players to the group. Each one gets every perk at once, with no need to grant anything to them individually.

  • oxidecarbon.usergroup add 76561198000000001 vip
  • oxidecarbon.usergroup add 76561198000000002 vip
vipVIP · rank 12 players added
Permissions
kits.kit.vipbackpacks.usequicksmelt.useskins.use
Players
…000001…000002
4

Remove a VIP

When a VIP subscription ends, remove the player from the group. They lose every VIP perk, and the group and its perks stay as they are.

  • oxidecarbon.usergroup remove 76561198000000002 vip

Check the result with oxidecarbon.show group vip.

vipVIP · rank 11 player removed
Permissions
kits.kit.vipbackpacks.usequicksmelt.useskins.use
Players
…000001…000002
That’s the whole pattern. Create a group, grant it permissions, then add or remove players. Moderators, builders, YouTubers and donor tiers all work the same way.

The default group

Every player is put in default automatically, including first-time joiners. Anything you grant to default is something everyone on the server can use.

Use it for features everyone gets

Starter kits, /home, a remover tool, or anything else every player should have.

oxidecarbon.grant group default kits.kit.starter

The admin group

Players with auth level 2 (ownerid) are added to admin automatically. Give admin-only plugin permissions to that group, not to individual players.

Carbon also adds auth level 1 players (moderatorid) to a moderator group.

Be careful with default. Granting an admin or “bypass” permission to default gives it to every player. If a player has something they shouldn’t, check oxidecarbon.show group default first.

Parent groups & inheritance

A group can have a parent. It gets everything the parent has, plus its own permissions. This makes tiers easy: VIP+ gets everything VIP has, so you only grant the extras.

vip_plusVIP+ (gets its own perms, everything from vip, and everything from default)
kits.kit.vipplusnteleportation.home.unlimitedkits.kit.vipbackpacks.usequicksmelt.useskins.use
vipThe group from the example above
kits.kit.vipbackpacks.usequicksmelt.useskins.use
defaultEveryone
kits.kit.starter

Set up the VIP+ tier

  • oxidecarbon.group add vip_plus "VIP+" 2

    Create the higher tier.

  • oxidecarbon.group parent vip_plus vip

    Child first, then parent. vip_plus now inherits from vip.

  • oxidecarbon.grant group vip_plus kits.kit.vipplus

    Grant only the extras.

  • oxidecarbon.usergroup add 76561198000000001 vip_plus

    Upgrade a player. Remove them from vip if you want, since they still get those perms through the parent.

Change once, update every tier. Grant a new perk to vip and vip_plus members get it as well. A group has one parent, but parents can chain: vip_max → vip_plus → vip.

Wildcards: many at once

End a permission with * to grant or revoke every permission that starts with that text.

  • oxidecarbon.grant group admin kits.*

    Every permission from the Kits plugin.

  • oxidecarbon.revoke group vip kits.*

    Remove all of them again.

  • oxidecarbon.grant group admin *

    Every permission from every plugin. Only for groups you fully trust, and never default.

Carbon extras

Carbon has a few extra tools that Oxide doesn’t.

  • carbon.show orphans

    List permissions still granted from plugins you’ve since removed.

  • carbon.cleanup orphans

    Revoke all of those leftover permissions in one go.

  • carbon.usergroup removeall vip

    Remove every player from a group, e.g. to reset a wipe-only VIP tier.

  • carbon.default_player_group

    Show or change which group new players join. It’s default unless you change it.

Troubleshooting

“Permission does not exist”

The plugin that owns the permission isn’t loaded, or the name has a typo. Plugins register their permissions when they load, so check the plugin is running, then run oxidecarbon.show perms and copy the exact name. Permission names are always lowercase.

I revoked a permission but the player still has it

revoke user only removes permissions granted to that player directly. If they get it from a group, including default or a parent group, they keep it. Run oxidecarbon.show user <player> to see their groups, then revoke it from the group or remove them from it.

“User not found” or the wrong player was picked

Use the player’s Steam ID (the 17-digit number starting with 7656). Names can change and can match more than one player. If you do use a name with spaces, wrap it in quotes: oxidecarbon.usergroup add "Some Player" vip. The player must have joined your server at least once.

The command does nothing in game

Use the F1 console, not chat, and make sure you have auth level 2 (ownerid). Otherwise, run the command from the server console or RCON.

Where are permissions saved? Should I back them up?

Oxide saves groups and players in oxide/data/oxide.groups.data and oxide/data/oxide.users.data. Back up both before big changes. Map wipes don’t touch them.

Carbon saves them in its data folder (carbon/data). You can switch to a SQLite database with carbon.migrate_perms_sql. Back up the data folder before big changes. Map wipes don’t touch it.

Where do I find a plugin’s permissions?

On the plugin’s page. Every ModPulse product page lists them in a Permissions section, with the same layout on every product. You can also run oxidecarbon.show perms to list everything loaded on your server.

Take your server further

High performance Rust plugins for Oxide / Carbon, with support on Discord.