The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →To give a Rust player access to a plugin feature, run oxide.grant user <name|Steam64ID> <permission> from the server console or RCON. For a maintainable setup, create a role, grant the permission to that role, then add players with oxide.usergroup add. The permission must be the exact node registered by the plugin, commonly written as pluginname.permission.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
Oxide (now commonly distributed as uMod) does not invent plugin permissions. A permission exists only after Oxide itself or a loaded plugin registers it, and the plugin must check that node before its command or feature is allowed.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What an Oxide permission is
An Oxide/uMod permission is a named capability string. A plugin registers one or more strings and checks them when a player attempts to use a command, menu, item, event or other feature. A typical node is epicstuff.use: epicstuff identifies the plugin and use describes the capability. The spelling shown in the plugin’s documentation is authoritative; do not substitute a similar-looking name.
The permission system is separate from Rust’s built-in administrator status. Being a server owner or moderator gives access to administrative commands, but it does not guarantee every plugin feature unless the plugin treats that status as sufficient or you grant the relevant node. Conversely, a player can receive one narrowly scoped plugin permission without becoming a Rust administrator.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Permissions are created by code or by Oxide itself. For example, a plugin author can register a node with permission.RegisterPermission("epicstuff.use", this); and then test it with player.HasPermission("epicstuff.use"). If the plugin is not loaded or registration fails, the node will not appear in the permission list and no grant can make the feature work.
Where to run permission commands
Use the live Rust server console or an authenticated RCON connection. Console execution is the least ambiguous option because it does not depend on a player’s chat permissions or command parser. Official Oxide guidance also describes command use through chat for supported games, but a Rust installation, permission configuration and command framework determine whether chat execution is enabled. If a chat attempt is rejected, run the same command in the server console or RCON instead.
Establish administrator access first
The account issuing administrative commands must have moderator or administrator access. Rust identifies owners by Steam64 ID; an owner entry can be established with the server’s ownerid configuration in users.cfg. Complete that owner or moderator setup before diagnosing a plugin permission. A denied oxide.grant command is an access problem, not evidence that the plugin node is wrong.
Use Steam64 IDs when names are ambiguous
Every command below accepts either a player name or a Steam64 ID. Names can change, collide, contain spaces or be unavailable when the player is offline. A Steam64 ID is stable and is the safer choice for automation, audits and offline administration.
Oxide permission command reference
Replace each angle-bracket value with a real value. Do not type the brackets.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
| Purpose | Command | What it changes or displays |
|---|---|---|
| Grant a node to one player | oxide.grant user <name|Steam64ID> <permission> |
Adds the node directly to that user. |
| Remove a node from one player | oxide.revoke user <name|Steam64ID> <permission> |
Removes a direct user grant. |
| Grant a node to a group | oxide.grant group <group> <permission> |
Gives the node to every member of the group. |
| Remove a node from a group | oxide.revoke group <group> <permission> |
Removes the group’s grant. |
| Create a group | oxide.group add <group> [title] [rank] |
Creates a named role. Title and rank are optional arguments. |
| Delete a group | oxide.group remove <group> |
Removes the group definition. |
| Set a parent group | oxide.group parent <group> <parentGroup> |
Makes the first group inherit the second group’s permissions. |
| Add a player to a group | oxide.usergroup add <name|Steam64ID> <group> |
Makes the player a member of the group. |
| Remove a player from a group | oxide.usergroup remove <name|Steam64ID> <group> |
Removes that membership. |
| Inspect one player | oxide.show user <name|Steam64ID> |
Shows the player’s groups and permissions, including useful evidence for troubleshooting. |
| Inspect one group | oxide.show group <group> |
Shows the group’s permissions and members. |
| Find holders of a node | oxide.show perm <permission> |
Shows users or groups associated with that permission. |
| List all groups | oxide.show groups |
Displays the group names currently defined. |
| List registered nodes | oxide.show perms |
Displays permissions currently registered by Oxide and loaded plugins. |
Command aliases
OxideMod documentation also uses o.* and perm.* aliases for the core permission commands. uMod-specific documentation shows corresponding umod.* forms. If an alias is not accepted by your server build, use the fully written oxide.* command shown above.
Recommended Free Tools
Recommended setup: create a role and grant one plugin feature
Group-based administration is the normal choice for staff, VIPs and other repeatable roles. One grant then applies to every member, and changing the role later does not require editing each user.
- Confirm administrative access. Log in to the server console or RCON with a moderator or owner account. If the command itself is rejected, fix the Rust owner or moderator configuration first.
- Load the plugin. Install or reload the plugin that owns the feature. A permission cannot be granted reliably before the plugin registers its nodes.
- Copy the exact node. Open the plugin’s permission list and copy the complete string, including punctuation and any prefix. For example, use
epicstuff.use, notepicstuffor a guessed variation. - Create a least-privilege group. For example:
oxide.group add vip "VIP" 0. The group name is the value used by later commands; the optional title and rank are supplied when you want them. - Grant only the needed node. Run
oxide.grant group vip epicstuff.use. Repeat this command only for other features the role genuinely needs. - Add a player. Run
oxide.usergroup add <Steam64ID> vip. Using the ID avoids name matching problems. - Verify the configuration. Check the role with
oxide.show group vip, the player withoxide.show user <Steam64ID>, and the node withoxide.show perm epicstuff.use. - Test with a non-admin account. An administrator may receive access through the admin group or server status, which can hide a missing plugin grant. Test the feature as the intended VIP or moderator role when possible.
- Remove temporary access. If you granted a broad permission or temporary admin membership while testing, revoke it after the test.
Copyable example
oxide.group add vip "VIP" 0
oxide.grant group vip epicstuff.use
oxide.usergroup add 76561198000000000 vip
oxide.show group vip
oxide.show user 76561198000000000
oxide.show perm epicstuff.useThe Steam64 value in this example is only a command-format example. Replace it with the actual player’s ID and keep the permission string exactly as documented by the plugin.
Direct user grants versus groups
A direct grant is useful for a one-off exception. Groups are better when several people share a role or when you expect the permission set to change.
| Decision point | Direct user grant | Group-based grant |
|---|---|---|
| Maintenance | Each user must be edited separately when the feature changes. | Change the group once and all members receive the new result. |
| Auditability | Exceptions can become scattered across many users. | Role membership and role permissions provide a clearer audit trail. |
| Inheritance | Does not provide a reusable parent role. | Can inherit permissions from a parent group. |
| Best use | Temporary access or an individual exception. | Staff, VIP, builder, event or other repeatable roles. |
| Blast radius | Normally limited to one account, unless that account is highly privileged. | A mistake affects every member, especially when wildcards are used. |
Granting an individual instead
For a one-time exception, run oxide.grant user <Steam64ID> <permission>. Confirm it with oxide.show user <Steam64ID>. When the exception ends, remove it with the matching oxide.revoke user command. Do not revoke a group permission when you intended to remove only a direct user grant.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Groups, inheritance and the default roles
Default Oxide groups
Oxide documents two default groups: admin and default. Players recognized as server administrators through the owner configuration are automatically assigned to admin. Every connecting player is assigned to default. The names of these default groups can be changed in oxide.config.json, so inspect your configuration if a server uses custom names.
Being in admin or default does not mean every plugin permission is automatically present. Plugins can choose how they treat those groups, and ordinary plugin nodes still need to be granted unless the plugin’s own defaults provide access.
Parent direction matters
A group inherits from its parent. The command oxide.group parent moderator default makes moderator inherit permissions assigned to default. It does not make default inherit from moderator. If a player appears to be in the right group but lacks a parent permission, inspect the direction with oxide.show group and correct the relationship.
Use inheritance for layers
A practical hierarchy is a base group with common, low-risk permissions and a child group for additional duties. For example, a server can place shared player features in a base role, then let a moderator role inherit those features and receive a small number of moderation nodes. Keep the parent role narrow: every child receives everything in it.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Wildcards: powerful but easy to overgrant
Oxide supports * to grant all permissions and prefix wildcards such as oxide.* for a permission family. A wildcard can be appropriate for a tightly controlled administrative role, but it is usually excessive for an ordinary staff or VIP group. Prefer explicit plugin nodes so a newly installed plugin does not silently become available to every member of that role.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Audit and remove broad grants
- Inspect the role with
oxide.show group <group>. - Inspect the player with
oxide.show user <Steam64ID>. - Look specifically for
*,oxide.*, temporary admin membership and unexpected parent groups. - Remove an unnecessary wildcard with
oxide.revoke group <group> *or revoke the exact prefix that was granted. - Replace it with the explicit nodes required by the role.
The final revoke command must match the value that was granted. If the broad access came from a parent group, remove it from the parent rather than trying to revoke an inherited permission from every child.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How plugin registration affects troubleshooting
A permission command changes Oxide’s access data; it does not create a capability that no plugin knows about. The normal sequence is:
- The plugin loads.
- The plugin registers a node such as
epicstuff.use. - A player invokes the feature.
- The plugin checks the player’s effective permissions, including direct grants, group grants and inherited grants.
- The plugin allows or denies the action.
If step two never occurs, oxide.show perms will not list the node. A typo in the grant command can therefore look similar to a plugin failure, while a failed plugin load can look similar to a permission problem. Check registration before adding increasingly broad grants.
Why a Rust plugin says “You don’t have permission”
The node is misspelled
Copy the node from the plugin’s documentation and compare it character by character with the grant. Then run oxide.show perms and confirm that the exact node is registered. Granting a plausible but nonexistent string has no effect.
The plugin is not loaded
Reload or fix the plugin, then run oxide.show perms again. An unloaded or failed plugin may not have registered any of its nodes. Do not treat the absence of a node as proof that the command syntax is wrong until the plugin load state is confirmed.
The player is not in the intended group
Run oxide.show user <Steam64ID> and verify the group name exactly. If the group is missing, add it with oxide.usergroup add <Steam64ID> <group>. If the player has several groups, check which one actually carries the node.
The group grant is on the wrong role
Run oxide.show group <group> and confirm that the permission is listed there. A common mistake is granting the node to moderator while the player belongs only to vip, or granting it to a parent that is not connected to the player’s group.
Parent inheritance is reversed
Remember that oxide.group parent <child> <parent> gives the child the parent’s permissions. If the command was entered in the opposite order, the expected access will not flow downward. Inspect the group definition and set the relationship again in the correct direction.
The command issuer lacks administrative access
If oxide.grant, oxide.group or oxide.show is itself denied, stop debugging the plugin node. Confirm that the account has moderator or owner access and that its Steam64 ID is correctly represented in the server’s owner configuration. Retry from the server console or authenticated RCON.
An administrator test is misleading
Testing only with an owner account can produce a false positive because the account may receive access through administrative status or the admin group. Test with a separate account that has only the intended group membership.
Why a grant appears to work but access is still too broad
Inspect effective access rather than only the last command you entered. A player can receive a node directly, through one or more groups, through a parent group or through a wildcard. Use oxide.show user, oxide.show group and oxide.show perm together to identify the source.
- Unexpected access for one player: check direct grants and temporary admin membership.
- Unexpected access for an entire role: inspect that role and every parent for
*or a broad prefix. - Access remains after revoking a direct grant: the player may still inherit the node from a group.
- Access disappears for everyone after one change: the node may have been granted only to a shared parent or group; restore the explicit role grant if that was unintended.
A practical permission-management checklist
- Keep a written list of each role and the exact nodes it needs.
- Use groups for repeatable roles and direct grants only for documented exceptions.
- Grant explicit plugin nodes instead of
*or broad prefixes whenever possible. - Use Steam64 IDs for scripts and for players whose names are ambiguous.
- After every change, verify the group, user and permission with the corresponding
oxide.showcommand. - Test with a non-admin account before announcing that a feature is ready.
- Review parent groups whenever a role’s access changes.
- Remove temporary grants and temporary administrator status immediately after testing.
- When a node is unknown, verify the plugin load and registration before changing user or group membership.
Quick command recipes
Give one player one feature
oxide.grant user 76561198000000000 epicstuff.use
oxide.show user 76561198000000000Create a moderator role with one plugin permission
oxide.group add moderator "Moderator" 0
oxide.grant group moderator epicstuff.use
oxide.usergroup add 76561198000000000 moderator
oxide.show group moderator
oxide.show user 76561198000000000Remove the feature from a role
oxide.revoke group moderator epicstuff.use
oxide.show group moderatorRemove a player from a role
oxide.usergroup remove 76561198000000000 moderator
oxide.show user 76561198000000000Check whether a node exists and who has it
oxide.show perms
oxide.show perm epicstuff.useBottom line for Rust server owners
Find the exact permission node registered by the loaded plugin, then grant it to a narrowly scoped group and add players to that group. Use direct user grants only for exceptions, verify every change with the oxide.show commands, and investigate plugin loading, group membership, inheritance and wildcards before handing out broader access.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
