{"id":1038,"date":"2021-09-23T16:50:31","date_gmt":"2021-09-23T16:50:31","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=1038"},"modified":"2026-06-15T19:22:27","modified_gmt":"2026-06-15T19:22:27","slug":"how-to-set-plugin-permission-on-your-rust-server","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/","title":{"rendered":"How to set uMod plugin permission on your Rust server"},"content":{"rendered":"\n

Installing a plugin on your Rust server is only half the job. Most Oxide and Carbon plugins do nothing until you explicitly grant the right people permission to use them. If you have ever dropped a plugin into oxide\/plugins\/<\/code>, reloaded it, and then watched it do absolutely nothing in-game, the missing piece is almost always permissions. This guide walks through the entire permission system from the ground up: the two built-in groups, the exact oxide.grant<\/code> and oxide.revoke<\/code> syntax, how groups and inheritance work, the pluginname.permission<\/code> node format, and why every one of these commands works identically whether you run Oxide\/uMod or Carbon.<\/p>\n\n\n\n

How the Oxide permission system works<\/h2>\n\n\n\n

Oxide (also known as uMod) is the long-established Rust modding framework, with the largest plugin library available \u2014 over 1,400 plugins on uMod alone. Its permission system is built on two simple concepts: permissions<\/strong> and groups<\/strong>. A permission is a single string that unlocks one capability of a plugin. A group is a named bucket of users that can hold a bundle of permissions. You can assign permissions directly to an individual player, or to a group that the player belongs to \u2014 and in practice, granting to a group is almost always the cleaner approach.<\/p>\n\n\n\n

When you install Oxide, it automatically creates two default groups<\/strong>: admin<\/code> and default<\/code>. Every player who connects is a member of default<\/code>, and any player with an auth level (an owner or moderator) is automatically placed in admin<\/code>. This is why so many plugins “just work” for admins out of the box but appear broken for regular players \u2014 the plugin author granted its core permissions to the admin<\/code> group, and the default<\/code> group has nothing. Your job as a server owner is to decide which capabilities the default<\/code> group (everyone) gets, and which you reserve for special groups like VIPs, supporters, or moderators.<\/p>\n\n\n\n

The pluginname.permission node format<\/h3>\n\n\n\n

Every permission in Oxide follows the same format: pluginname.permission<\/code>. The first part is the plugin’s registered name (lowercased), and the second part is the specific capability that the plugin’s author defined. So a plugin called CoolPlugin might register coolplugin.use<\/code> for general access, while the Vanish plugin registers vanish.allow<\/code> for the players allowed to go invisible. There is no universal list \u2014 each plugin documents its own permission nodes, usually in its description page or config. The pattern, however, never changes:<\/p>\n\n\n\n

coolplugin.use      # general access to CoolPlugin\nvanish.allow        # allowed to use the Vanish plugin\nremovertool.normal  # example node: standard remove access\nserverrewards.use   # example node: access the rewards store<\/code><\/pre>\n\n\n\n
To find a plugin’s exact nodes, read its documentation first, then verify in-game with the inspection commands covered later in this guide (oxide.show perms <\/code> and oxide.show perm <\/code>). Never assume a node name \u2014 a typo in a permission string fails silently, and that is the single most common reason a “broken” plugin is really just a misspelled grant.<\/p>\n\n\n\n
Granting and revoking permissions to a user<\/h2>\n\n\n\n
The most direct way to give a single player access to a plugin is to grant the permission to that user. Oxide accepts either the player’s name or their SteamID64 (the 17-digit number, for example 76561197854018763<\/code>). The SteamID64 is always the safer choice because names change and can contain spaces or special characters that confuse the parser. You can read a connected player’s SteamID64 from the ID<\/strong> column of the status<\/code> command.<\/p>\n\n\n\n
# Grant a permission to a single user (by name OR SteamID64)\noxide.grant  user 76561197854018763 coolplugin.use\noxide.grant  user \"PlayerName\" coolplugin.use\n\n# Revoke that permission from the user\noxide.revoke user 76561197854018763 coolplugin.use\noxide.revoke user \"PlayerName\" coolplugin.use<\/code><\/pre>\n\n\n\n
Direct user grants are perfect for one-off cases \u2014 handing a single content creator access to a special command, or testing a permission before you roll it out. But they get unmanageable fast. If you grant ten permissions to twenty VIPs individually, you now have two hundred grants to track, and revoking VIP status from one player means hunting down ten separate commands. That is exactly the problem groups solve.<\/p>\n\n\n\n
Working with groups<\/h2>\n\n\n\n
Groups let you define a permission set once and then move players in and out of it. The workflow is: create a group, grant the group its permissions, then add users to the group. When a player joins the group they inherit every permission the group holds; remove them and the access is gone instantly \u2014 no need to revoke each node one by one.<\/p>\n\n\n\n
Creating and deleting groups<\/h3>\n\n\n\n
# Create a new group\noxide.group add supporters\n\n# Remove a group entirely\noxide.group remove supporters\n\n# Set a display title and a rank number for the group\noxide.group set supporters \"[Server Supporters]\" 1<\/code><\/pre>\n\n\n\n
The oxide.group set<\/code> command assigns a human-readable title (often used by chat plugins to show a tag next to a player’s name) and a numeric rank that some plugins use to order groups. The admin<\/code> and default<\/code> groups already exist and should not be deleted \u2014 they are part of the framework’s core behavior.<\/p>\n\n\n\n
Granting permissions to a group<\/h3>\n\n\n\n
Granting and revoking for a group uses the same oxide.grant<\/code> \/ oxide.revoke<\/code> verbs you saw for users \u2014 you just swap user<\/code> for group<\/code>:<\/p>\n\n\n\n
# Grant a permission to a whole group\noxide.grant  group supporters coolplugin.use\noxide.grant  group admin      coolplugin.use\n\n# Revoke a permission from a group\noxide.revoke group admin      coolplugin.use<\/code><\/pre>\n\n\n\n
A very common pattern is granting a capability to the default<\/code> group so that every<\/em> player on your server can use it \u2014 for example, letting everyone use a teleport-to-home plugin or a player-side remove tool. Reserve more powerful nodes for purpose-built groups, and keep truly destructive admin tools on the admin<\/code> group only.<\/p>\n\n\n\n
Adding and removing users from groups<\/h3>\n\n\n\n
Once a group holds the permissions you want, you move players in and out with oxide.usergroup<\/code>. As with grants, you can reference a player by name or SteamID64.<\/p>\n\n\n\n
# Add a user to a group\noxide.usergroup add    76561197854018763 supporters\noxide.usergroup add    \"PlayerName\"      supporters\n\n# Remove a user from a group\noxide.usergroup remove 76561197854018763 supporters\noxide.usergroup remove \"PlayerName\"      supporters<\/code><\/pre>\n\n\n\n
This is where the group model pays off. Selling a VIP rank? One oxide.usergroup add<\/code> command grants the buyer everything the VIP group offers. Refund or expiry? One oxide.usergroup remove<\/code> and they lose it all. Most donation and store plugins automate exactly these two commands behind the scenes.<\/p>\n\n\n\n
Group inheritance (parents)<\/h2>\n\n\n\n
Oxide supports group inheritance through parents. A child group inherits every permission its parent holds, on top of its own. This lets you build tiered ranks without re-granting shared permissions at every level.<\/p>\n\n\n\n
# Make tier_2 inherit everything tier_1 has\noxide.group parent tier_2 tier_1<\/code><\/pre>\n\n\n\n
Picture a three-tier donor system. You grant baseline perks to tier_1<\/code>, then set tier_2<\/code>‘s parent to tier_1<\/code> and add only the extra perks; tier_2<\/code> members automatically get the baseline plus their own. Set tier_3<\/code>‘s parent to tier_2<\/code> and it stacks again. When you later add a new perk for everyone, you grant it once at tier_1<\/code> and it cascades upward through the chain.<\/p>\n\n\n\n
Inspecting permissions and groups<\/h2>\n\n\n\n
You cannot manage what you cannot see. Oxide’s oxide.show<\/code> family of commands lets you audit exactly who has what. Use these constantly \u2014 they are how you confirm a grant actually landed and how you debug a “permission isn’t working” report.<\/p>\n\n\n\n
oxide.show groups               # list every group\noxide.show group admin          # show the members of a group\noxide.show user       # show a user's groups + permissions\noxide.show perms     # show all permissions held by a group\noxide.show perm coolplugin.use   # show who\/what has a specific permission<\/code><\/pre>\n\n\n\n
A reliable troubleshooting routine: run oxide.show user \"PlayerName\"<\/code> to see the player’s groups and direct permissions, then oxide.show perms <\/code> on each of their groups to confirm the node is actually present and spelled correctly. Nine times out of ten the issue is a misspelled node, a player who isn’t in the group they should be, or a plugin that didn’t reload after a config change.<\/p>\n\n\n\n
Command reference table<\/h2>\n\n\n\n
\n
Command<\/th>What it does<\/th><\/tr><\/thead>
oxide.grant user  <\/code><\/td>Grant a permission to one player<\/td><\/tr>\n
oxide.revoke user  <\/code><\/td>Revoke a permission from one player<\/td><\/tr>\n
oxide.grant group  <\/code><\/td>Grant a permission to a whole group<\/td><\/tr>\n
oxide.revoke group  <\/code><\/td>Revoke a permission from a group<\/td><\/tr>\n
oxide.group add <\/code><\/td>Create a new group<\/td><\/tr>\n
oxide.group remove <\/code><\/td>Delete a group<\/td><\/tr>\n
oxide.group set  \"\" <rank><\/code><\/td><td>Set a group’s display title and rank<\/td><\/tr>\n<tr><td><code>oxide.group parent <child> <parent><\/code><\/td><td>Make a group inherit from another<\/td><\/tr>\n<tr><td><code>oxide.usergroup add <name|ID> <group><\/code><\/td><td>Add a player to a group<\/td><\/tr>\n<tr><td><code>oxide.usergroup remove <name|ID> <group><\/code><\/td><td>Remove a player from a group<\/td><\/tr>\n<tr><td><code>oxide.show ...<\/code><\/td><td>Inspect groups, users and permissions<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Carbon uses the exact same commands<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Carbon is the modern alternative modding framework for Rust. The official Rust wiki describes it as “a modern modding framework for the game Rust responsible for handling background operations and running custom plugins and extensions with maximum performance.” Crucially for this guide, Carbon was designed for seamless migration from Oxide: it offers an identical folder structure and automatic data migration tools, uses Harmony, and requires no additional patches to run existing Oxide plugins (community sources report roughly 99% Oxide-plugin compatibility).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What that means in practice is that <strong>every permission command above works unchanged on Carbon<\/strong>. Carbon accepts the full <code>oxide.*<\/code> command surface \u2014 the same <code>admin<\/code> and <code>default<\/code> groups, the same <code>pluginname.permission<\/code> node format, the same grant\/revoke\/group\/usergroup verbs. On top of that, Carbon exposes a shorter <code>o.<\/code> alias (which also works on Oxide):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># These are equivalent on Carbon (and the o. alias works on Oxide too)\noxide.grant group vips coolplugin.use\no.grant     group vips coolplugin.use\n\n# Reloading: o.reload works on both; Carbon also has a native command\no.reload CoolPlugin\ncarbon.reload CoolPlugin<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">So if you migrate a server from Oxide to Carbon, your permission knowledge transfers one-to-one. The grants, groups and inheritance you already configured carry over via Carbon’s data migration, and you keep typing the same commands. The only practical difference you’ll notice is performance: Carbon uses dynamic hook loading (only the hooks a plugin actually calls are loaded), which the community reports yields higher FPS, lower RAM use and faster boot times. Carbon-specific aliases beyond <code>o.<\/code> and <code>carbon.reload<\/code> may exist \u2014 check the current Carbon docs before relying on them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A note on wildcards<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You will often see people suggest wildcard permissions \u2014 <code>*<\/code> to grant everything, or <code>pluginname.*<\/code> to grant all of one plugin’s nodes at once. These patterns are commonly used in the community, but support and exact behavior can vary by plugin, so treat them as something to verify rather than assume. The safe, predictable approach is to grant the specific nodes a plugin documents. If you do experiment with a wildcard, confirm the result immediately with <code>oxide.show perms <group><\/code> so you know exactly what you handed out \u2014 accidentally granting <code>*<\/code> to the <code>default<\/code> group would give every player on your server full plugin access.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Putting it together: a real VIP setup<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here is a complete, copy-pasteable example that creates a VIP rank, gives it a couple of plugin capabilities, tags it for chat, and enrolls a player. Run these from your WebRCON console or the in-game F1 console (with an auth level):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) create the group\noxide.group add vips\noxide.group set vips \"[VIP]\" 5\n\n# 2) grant the perks the VIP rank should include\noxide.grant group vips coolplugin.use\noxide.grant group vips vanish.allow\n\n# 3) enroll a player by SteamID64\noxide.usergroup add 76561197854018763 vips\n\n# 4) verify it landed\noxide.show perms vips\noxide.show user 76561197854018763<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That’s the entire lifecycle. To sell a second tier later, create <code>vips_plus<\/code>, set its parent to <code>vips<\/code>, grant only the extra perks, and the higher tier automatically includes everything the base VIP rank offers. When you’re ready to scale this kind of configured, plugin-ready setup without managing the underlying machine, our <a href=\"https:\/\/xgamingserver.com\/rust-hosting-server\">managed Rust server plans<\/a> ship with Oxide\/Carbon support and one-click control so you can spend your time on permissions and gameplay instead of system administration. For framework installation and panel-specific steps, see the <a href=\"https:\/\/xgamingserver.com\/docs\/rust\">Rust documentation<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Important: reinstall your framework after every update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One operational gotcha catches every Rust admin eventually. When Facepunch ships a server update \u2014 including the monthly force wipe, such as the June 4, 2026 “Built Different” update \u2014 the update <strong>overwrites Oxide and Carbon files<\/strong>. After any update or wipe you must reinstall the framework before your plugins (and therefore your permissions) will load again. Your permission data itself survives in the data files, but the framework binary needs replacing. On force-wipe day, Carbon is typically patched fastest (often within hours), which matters if you’re racing to be online for the first-player rush. See our <a href=\"https:\/\/xgamingserver.com\/blog\/rust-built-different-update-server-admins\/\">Built Different update breakdown<\/a> for the full wipe-day checklist.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between oxide.grant user and oxide.grant group?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><code>oxide.grant user <name|SteamID64> <permission><\/code> attaches a permission directly to one specific player. <code>oxide.grant group <group> <permission><\/code> attaches it to a group, and every member of that group inherits it. Use user grants for one-off or testing cases; use group grants for anything you’ll repeat (VIPs, moderators, server-wide perks) because you can then manage access by simply moving players in and out of the group with <code>oxide.usergroup<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What are the default and admin groups in Oxide?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Oxide automatically creates two built-in groups when it installs. <code>default<\/code> contains every player who connects \u2014 grant a permission here and the whole server gets it. <code>admin<\/code> contains players with an auth level (owners and moderators), and they’re placed in it automatically. Many plugins ship their admin-only nodes pre-granted to the <code>admin<\/code> group, which is why those plugins work for you but appear to do nothing for regular players until you grant the relevant node to <code>default<\/code> or another group.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I find a plugin’s permission node?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Permission nodes always follow the <code>pluginname.permission<\/code> format, but the exact string is defined by each plugin’s author. Check the plugin’s documentation page first, then confirm in-game with <code>oxide.show perm <node><\/code> or by inspecting a group with <code>oxide.show perms <group><\/code>. Never guess \u2014 a misspelled node fails silently, with no error, which is the most common reason admins think a plugin is broken when the grant simply never matched a real permission.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do Oxide permission commands work on Carbon?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Carbon supports the same command surface as Oxide, including the full <code>oxide.*<\/code> permission commands, the same <code>admin<\/code>\/<code>default<\/code> groups, and the same <code>pluginname.permission<\/code> format. Carbon also adds a shorter <code>o.<\/code> alias (for example <code>o.grant<\/code>), which works on Oxide as well. Because Carbon offers identical folder structure and automatic data migration, your existing permission setup transfers when you switch frameworks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I grant a permission to every player at once?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes \u2014 grant it to the <code>default<\/code> group with <code>oxide.grant group default <permission><\/code>. Since every connected player is a member of <code>default<\/code>, this is the standard way to enable a plugin capability server-wide. Just be deliberate about it: only put low-risk, player-friendly nodes on <code>default<\/code>, and keep administrative or destructive capabilities on the <code>admin<\/code> group or a dedicated moderator group.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why did my permissions stop working after a Rust update?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A Facepunch update overwrites the Oxide and Carbon framework files, so after any update or monthly force wipe you must reinstall the framework before plugins will load. Your permission and group data is stored separately and generally survives, but with no framework running, no plugin checks permissions, so everything appears to be gone. Reinstall Oxide or Carbon, reload your plugins, and your existing grants take effect again. Carbon is usually patched first on wipe day.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related Rust admin guides<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/xgamingserver.com\/blog\/rust-rcon-server-console-commands\/\">Rust RCON & server console commands<\/a> \u2014 where to run these permission commands remotely.<\/li>\n<li><a href=\"https:\/\/xgamingserver.com\/blog\/top-10-admin-plugins-for-your-rust-server\/\">Top 10 admin plugins for your Rust server<\/a> \u2014 plugins whose permissions you’ll be granting.<\/li>\n<li><a href=\"https:\/\/xgamingserver.com\/blog\/how-to-see-who-is-on-your-rust-server\/\">How to see who is on your Rust server<\/a> \u2014 read SteamID64s for user grants.<\/li>\n<li><a href=\"https:\/\/xgamingserver.com\/blog\/how-to-modify-the-gather-rate-on-your-rust-server\/\">How to modify the gather rate<\/a> \u2014 a permission-gated plugin in action.<\/li>\n<\/ul>\n\n\n<!-- xg-tools-mesh -->\n\n<div class=\"wp-block-group xg-tools-box is-layout-flow wp-block-group-is-layout-flow\" style=\"border:1px solid rgba(255,255,255,.1);border-radius:12px;padding:18px 22px;margin-top:8px;background:rgba(76,175,80,.04);\">\n<h3 class=\"wp-block-heading\">Free Rust Tools<\/h3>\n<p class=\"wp-block-paragraph\">Speed up your server with our free Rust tools:<\/p>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/xgamingserver.com\/tools\/rust\/raid-calculator\">Raid Calculator<\/a><\/li><li><a href=\"https:\/\/xgamingserver.com\/tools\/rust\/gunpowder-calculator\">Gunpowder Calculator<\/a><\/li><li><a href=\"https:\/\/xgamingserver.com\/tools\/rust\/decay-calculator\">Decay Calculator<\/a><\/li><li><a href=\"https:\/\/xgamingserver.com\/tools\/rust\/sulfur-calculator\">Sulfur Calculator<\/a><\/li><\/ul>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"<p>Installing a plugin on your Rust server is only half the job. Most Oxide and Carbon plugins do nothing until you explicitly grant the right people permission to use them. If you have ever dropped a plugin into oxide\/plugins\/, reloaded it, and then watched it do absolutely nothing in-game, the missing piece is almost always […]<\/p>\n","protected":false},"author":3,"featured_media":1049,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[13],"tags":[],"class_list":["post-1038","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-rust-server-docs"],"blocksy_meta":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v24.5 (Yoast SEO v26.7) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to set uMod plugin permission on your Rust server - XGamingServer<\/title>\n<meta name=\"description\" content=\"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to set uMod plugin permission on your Rust server\" \/>\n<meta property=\"og:description\" content=\"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\" \/>\n<meta property=\"og:site_name\" content=\"XGamingServer\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/web.facebook.com\/xgamingserver69\/\" \/>\n<meta property=\"article:published_time\" content=\"2021-09-23T16:50:31+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-15T19:22:27+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions-1024x576.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"576\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Youssef Ayman\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@xgamingserver\" \/>\n<meta name=\"twitter:site\" content=\"@xgamingserver\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Youssef Ayman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\"},\"author\":{\"name\":\"Youssef Ayman\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/d76089853704ac189e01449b0e449e3e\"},\"headline\":\"How to set uMod plugin permission on your Rust server\",\"datePublished\":\"2021-09-23T16:50:31+00:00\",\"dateModified\":\"2026-06-15T19:22:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\"},\"wordCount\":2219,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg\",\"articleSection\":[\"Rust\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\",\"url\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\",\"name\":\"How to set uMod plugin permission on your Rust server - XGamingServer\",\"isPartOf\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg\",\"datePublished\":\"2021-09-23T16:50:31+00:00\",\"dateModified\":\"2026-06-15T19:22:27+00:00\",\"description\":\"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.\",\"breadcrumb\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage\",\"url\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg\",\"contentUrl\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg\",\"width\":1920,\"height\":1080},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/xgamingserver.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Rust\",\"item\":\"https:\/\/xgamingserver.com\/blog\/category\/rust-server-docs\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"How to set uMod plugin permission on your Rust server\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#website\",\"url\":\"https:\/\/xgamingserver.com\/blog\/\",\"name\":\"XGamingServer\",\"description\":\"Dedicated Game Server Hosting\",\"publisher\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/xgamingserver.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#organization\",\"name\":\"XGamingServer\",\"url\":\"https:\/\/xgamingserver.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2020\/09\/logo.svg\",\"contentUrl\":\"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2020\/09\/logo.svg\",\"width\":\"1024\",\"height\":\"1024\",\"caption\":\"XGamingServer\"},\"image\":{\"@id\":\"https:\/\/xgamingserver.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/web.facebook.com\/xgamingserver69\/\",\"https:\/\/x.com\/xgamingserver\",\"https:\/\/www.instagram.com\/xgamingserver\/\",\"https:\/\/www.linkedin.com\/company\/xgamingserver\/\",\"https:\/\/www.pinterest.com\/xgamingserver\/\",\"https:\/\/www.youtube.com\/channel\/UCHnOtWxpzaL2r3jM9Jm40EQ\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/d76089853704ac189e01449b0e449e3e\",\"name\":\"Youssef Ayman\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/fa92e71017a2bb7ab969b798cba0c8f3f827d2d4733dbe2cacf7f195db920fe1?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/fa92e71017a2bb7ab969b798cba0c8f3f827d2d4733dbe2cacf7f195db920fe1?s=96&d=mm&r=g\",\"caption\":\"Youssef Ayman\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How to set uMod plugin permission on your Rust server - XGamingServer","description":"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/","og_locale":"en_US","og_type":"article","og_title":"How to set uMod plugin permission on your Rust server","og_description":"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.","og_url":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/","og_site_name":"XGamingServer","article_publisher":"https:\/\/web.facebook.com\/xgamingserver69\/","article_published_time":"2021-09-23T16:50:31+00:00","article_modified_time":"2026-06-15T19:22:27+00:00","og_image":[{"width":1024,"height":576,"url":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions-1024x576.jpg","type":"image\/jpeg"}],"author":"Youssef Ayman","twitter_card":"summary_large_image","twitter_creator":"@xgamingserver","twitter_site":"@xgamingserver","twitter_misc":{"Written by":"Youssef Ayman","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#article","isPartOf":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/"},"author":{"name":"Youssef Ayman","@id":"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/d76089853704ac189e01449b0e449e3e"},"headline":"How to set uMod plugin permission on your Rust server","datePublished":"2021-09-23T16:50:31+00:00","dateModified":"2026-06-15T19:22:27+00:00","mainEntityOfPage":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/"},"wordCount":2219,"commentCount":3,"publisher":{"@id":"https:\/\/xgamingserver.com\/blog\/#organization"},"image":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage"},"thumbnailUrl":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg","articleSection":["Rust"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/","url":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/","name":"How to set uMod plugin permission on your Rust server - XGamingServer","isPartOf":{"@id":"https:\/\/xgamingserver.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage"},"image":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage"},"thumbnailUrl":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg","datePublished":"2021-09-23T16:50:31+00:00","dateModified":"2026-06-15T19:22:27+00:00","description":"uMod (oxide) Plugin permission give admins the ability to allow or deny specific plugins to other players.","breadcrumb":{"@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#primaryimage","url":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg","contentUrl":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg","width":1920,"height":1080},{"@type":"BreadcrumbList","@id":"https:\/\/xgamingserver.com\/blog\/how-to-set-plugin-permission-on-your-rust-server\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/xgamingserver.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Rust","item":"https:\/\/xgamingserver.com\/blog\/category\/rust-server-docs\/"},{"@type":"ListItem","position":3,"name":"How to set uMod plugin permission on your Rust server"}]},{"@type":"WebSite","@id":"https:\/\/xgamingserver.com\/blog\/#website","url":"https:\/\/xgamingserver.com\/blog\/","name":"XGamingServer","description":"Dedicated Game Server Hosting","publisher":{"@id":"https:\/\/xgamingserver.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/xgamingserver.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/xgamingserver.com\/blog\/#organization","name":"XGamingServer","url":"https:\/\/xgamingserver.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/xgamingserver.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2020\/09\/logo.svg","contentUrl":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2020\/09\/logo.svg","width":"1024","height":"1024","caption":"XGamingServer"},"image":{"@id":"https:\/\/xgamingserver.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/web.facebook.com\/xgamingserver69\/","https:\/\/x.com\/xgamingserver","https:\/\/www.instagram.com\/xgamingserver\/","https:\/\/www.linkedin.com\/company\/xgamingserver\/","https:\/\/www.pinterest.com\/xgamingserver\/","https:\/\/www.youtube.com\/channel\/UCHnOtWxpzaL2r3jM9Jm40EQ"]},{"@type":"Person","@id":"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/d76089853704ac189e01449b0e449e3e","name":"Youssef Ayman","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/xgamingserver.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/fa92e71017a2bb7ab969b798cba0c8f3f827d2d4733dbe2cacf7f195db920fe1?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fa92e71017a2bb7ab969b798cba0c8f3f827d2d4733dbe2cacf7f195db920fe1?s=96&d=mm&r=g","caption":"Youssef Ayman"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/xgamingserver.com\/blog\/wp-content\/uploads\/2021\/09\/permissions.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/posts\/1038","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/comments?post=1038"}],"version-history":[{"count":10,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/posts\/1038\/revisions"}],"predecessor-version":[{"id":22569,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/posts\/1038\/revisions\/22569"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/media\/1049"}],"wp:attachment":[{"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/media?parent=1038"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/categories?post=1038"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xgamingserver.com\/blog\/wp-json\/wp\/v2\/tags?post=1038"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}