iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
To give a Rust player access to a plugin feature, run oxide.grant user <name|Steam64ID> <permission> from the server console or RCON, using the exact permission node documented by that plugin. For a maintainable setup, create a group, grant the node to the group, and add players with oxide.usergroup add <name|Steam64ID> <group>. Oxide permissions are named capabilities: a plugin must register a node before anyone can receive it, and the plugin checks that node when the player uses a command or feature.
What Oxide permissions control
Oxide, also called uMod in current documentation, does not use one universal list of abilities. Permissions are strings supplied by Oxide itself or registered by an installed plugin. A typical plugin node follows the pattern pluginname.permission, such as epicstuff.use. The exact spelling, capitalization, and punctuation matter.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →When a plugin loads, it can register a node through the API’s permission.RegisterPermission(...) call. When a player attempts an operation, plugin code commonly checks the player’s access with player.HasPermission(...). If the plugin is not loaded or failed before registration, its nodes will not appear in the permission list and grants cannot make its feature work.
Permissions are separate from Rust’s built-in administrator status. An owner or moderator may be able to run server commands while still lacking a plugin-specific node, and a regular player can receive a narrowly scoped plugin node without becoming a server administrator.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Where to run permission commands
Use the Rust server console or a compatible RCON client. You need moderator or administrator access to issue administrative commands. If owner access has not yet been established, Rust’s command guidance uses the player’s Steam64 ID and an ownerid entry in users.cfg. Establish that server-level access first; otherwise the permission command itself may be rejected before Oxide evaluates the plugin node.
Some Oxide-supported games also accept these commands through chat, but for a Rust server the console or RCON is the dependable administrative path. Enter one command per line and omit the angle brackets shown in the examples.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThe essential command reference
The commands below use the standard oxide prefix. Use the permission string exactly as it appears in the plugin’s documentation.
| Purpose | Command |
|---|---|
| Grant one player a permission | oxide.grant user <name|Steam64ID> <permission> |
| Revoke one player’s permission | oxide.revoke user <name|Steam64ID> <permission> |
| Grant a permission to a group | oxide.grant group <group> <permission> |
| Revoke a permission from a group | oxide.revoke group <group> <permission> |
| Create a group | oxide.group add <group> [title] [rank] |
| Remove a group | oxide.group remove <group> |
| Set a parent group | oxide.group parent <group> <parentGroup> |
| Add a player to a group | oxide.usergroup add <name|Steam64ID> <group> |
| Remove a player from a group | oxide.usergroup remove <name|Steam64ID> <group> |
| Show one player’s permissions | oxide.show user <name|Steam64ID> |
| Show a group’s permissions and members | oxide.show group <group> |
| Show who has a permission | oxide.show perm <permission> |
| List groups | oxide.show groups |
| List registered permissions | oxide.show perms |
In every command, text inside angle brackets is a placeholder, not text to type. Replace <name|Steam64ID> with either the player’s current name or their 64-bit Steam identifier. Replace <group> with the group name you created, and replace <permission> with the complete node. A Steam64 ID is generally the safer identifier because names can change or be similar. Run each command separately so an error is easy to identify.
Oxide documentation also describes o.* and perm.* aliases for core permission commands. uMod-specific documentation shows the corresponding umod.* forms. If a shortened prefix is not accepted by your installation, use the full oxide command.
Give one player access directly
A direct grant is appropriate for a one-time exception, a test account, or a single player who should not join a broader role. The player can be identified by their current name or, preferably, their stable Steam64 ID.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Install or load the plugin that provides the feature.
- Read the plugin’s permission list and copy the exact node. For an illustrative node, use
epicstuff.useonly if that is the node the plugin documents. - Run
oxide.grant user 76561198000000000 epicstuff.use, replacing the example Steam64 ID and node with the real values. - Confirm the resulting entries with
oxide.show user 76561198000000000. - Have the player retry the feature. If it still fails, follow the troubleshooting section rather than granting administrator access as a workaround.
To undo the exception, run oxide.revoke user 76561198000000000 epicstuff.use. Revoking the node removes the direct grant; it does not remove access the player receives through a group or another inherited permission.
Use a group for staff, VIPs, or other roles
Groups are the normal choice when several players need the same capabilities. You change the role once instead of maintaining a list of individual grants, and membership provides an auditable explanation for why a player has access.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Create the role
Choose a clear name such as moderator or vip. Create it with oxide.group add moderator. The command also accepts optional title and rank arguments: oxide.group add moderator "Server Moderator" 10. Use those optional values only when your server’s role design needs them.
Grant only the required nodes
For each feature, run a separate group grant, for example oxide.grant group moderator epicstuff.use. Repeat for other documented nodes, but do not assume that a plugin’s command permission automatically includes every feature. Copy each node from the plugin’s own permission list.
Add players to the role
Run oxide.usergroup add 76561198000000000 moderator for each player. A name works, but a Steam64 ID avoids ambiguity when names change or two players use similar names. Confirm membership and inherited access with oxide.show group moderator and oxide.show user 76561198000000000.
Remove a player or retire the role
Remove an individual with oxide.usergroup remove 76561198000000000 moderator. If the role is no longer needed, first remove or migrate its members, then run oxide.group remove moderator. Removing the group also removes the role’s grants and membership record; it does not change permissions granted elsewhere.
A complete group setup example
Suppose a plugin documents epicstuff.use and you want a reusable VIP role. First verify that the plugin is loaded and that the node appears in oxide.show perms. Create the role with oxide.group add vip, then grant the node with oxide.grant group vip epicstuff.use. Add a player with oxide.usergroup add 76561198000000000 vip.
Check the result using oxide.show group vip and oxide.show user 76561198000000000. If the player can use the feature, repeat the add command for other members rather than issuing separate grants. If the plugin later needs another documented capability, add that node to vip once. To remove the capability from every VIP, run oxide.revoke group vip epicstuff.use; to remove only one player, remove that player from the group.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Default groups and inheritance
Oxide documents two default groups: admin and default. Players recognized as server administrators through ownerid 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 do not assume a server has retained the stock names.
A group can inherit from a parent group. The direction matters: oxide.group parent moderator default makes moderator inherit all permissions assigned to default. It does not make default inherit from moderator. Oxide’s group model is cumulative, so a player’s effective permissions can come from direct grants, every group they belong to, and each parent in the inheritance chain.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Keep inheritance shallow and intentional. A useful pattern is a baseline group for permissions that every player should have, with narrowly defined staff roles above it. Before changing a parent, inspect both groups with oxide.show group so a harmless-looking relationship does not broaden access unexpectedly.
Wildcards: powerful but risky
Oxide supports * as an all-permissions wildcard and prefix wildcards such as oxide.* for a family of nodes. A wildcard can be useful for a role that genuinely needs the entire matching scope, but it is much broader than a single plugin node.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Use explicit nodes such as
pluginname.usefor ordinary VIP and staff roles. - Review wildcard grants before investigating a permission leak; the apparent source may be a group rather than the plugin you are testing.
- Do not leave temporary wildcard or administrator access in place after testing.
- When a role’s responsibilities change, revoke the wildcard and replace it with the smallest set of documented nodes.
The least-privilege approach reduces the blast radius of a plugin bug, an account compromise, or a mistaken command while making an audit easier.
Direct grants versus groups
| Decision factor | Direct user grant | Group-based grant |
|---|---|---|
| Maintenance | Every change is made separately for each affected player. | One grant or revoke updates the role for all members. |
| Auditability | Exceptions can become scattered across user records. | Role membership shows the administrative reason for access. |
| Inheritance | The user can receive direct nodes but does not define a reusable parent role. | A child role can inherit permissions from a parent group. |
| Blast radius | An explicit node limits access to one account and one capability. | A group affects every member; wildcards can broaden it further. |
Use a direct grant for an isolated exception. Use a group when the same permission belongs to a role, when you expect membership to change, or when you need a clear audit trail.
Verify a permission before and after granting it
- Run
oxide.show perms. Confirm that the node exists in the registered list. If it is absent, the plugin may be unloaded, failed during startup, or using a different node than the one you copied. - Run
oxide.show group <group>to inspect the group’s permissions and members. - Run
oxide.show user <name|Steam64ID>to inspect the player’s direct and group-related access. - Run
oxide.show perm <permission>to see which users or groups currently have that node. - Test with a non-administrator account if possible. An administrator can appear to work because of broad administrative access, masking a missing plugin grant.
- After testing, remove temporary broad grants and retain only the role or direct node the player actually needs.
Use the views together rather than relying on a single success message. The group view answers whether the node is attached to the role, the user view shows whether the player belongs to that role or has a direct exception, and the permission view reveals every account or group currently associated with the node.
Troubleshoot “You don’t have permission”
The node is misspelled or belongs to another plugin
Compare the command with the plugin’s permission documentation character by character. Run oxide.show perms and use the registered spelling. A plausible-looking node is not valid merely because it follows the usual pluginname.permission pattern.
The plugin is not loaded
If the node is missing from oxide.show perms, check that the plugin is installed and loaded successfully. A plugin that failed to load cannot register its permissions, so granting a guessed node has no effect. Resolve the load failure, then check the registered list again.
The player is not in the group you changed
A successful group grant affects members of that group, not every player on the server. Run oxide.show group <group> and add the player with oxide.usergroup add <name|Steam64ID> <group> if necessary. Also run oxide.show user <name|Steam64ID> to catch a typo in the account name or Steam64 ID.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Inheritance points the wrong way
Check the parent relationship. oxide.group parent child parent gives the child the parent’s permissions. Reversing those names changes which role receives access. Inspect both groups after correcting the relationship.
Recommended Free Tools
The administrative command itself is denied
If the server rejects oxide.grant before changing any record, this is an access problem, not a plugin-permission problem. Confirm console or RCON authentication and verify that the account has the required moderator or administrator status. If owner access is missing, establish it with the server’s Steam64 ID and ownerid entry in users.cfg before retrying.
A wildcard or temporary admin grant is confusing the test
Inspect the player’s groups and the permission’s owners with oxide.show user, oxide.show group, and oxide.show perm. Revoke unnecessary wildcard nodes with oxide.revoke group <group> <permission> or remove temporary direct access with the corresponding oxide.revoke user command. Retest from a least-privileged account.
A repeatable least-privilege workflow
For each new plugin feature, use this sequence:
- Confirm you can administer the server from its console or RCON connection.
- Install or load the plugin and verify that it registers its permissions.
- Copy the exact node from the plugin documentation instead of inventing one.
- Decide whether the access is a one-off exception or a reusable role.
- For a role, create the group, grant only the needed nodes, and add players to it.
- For an exception, grant the node directly to the player’s Steam64 ID.
- Verify the group, user, and permission views with the
oxide.showcommands. - Test the feature as a non-admin account when possible.
- Revoke temporary administrator, wildcard, or test grants as soon as the test ends.
This process separates server-level administration from plugin-level capability, keeps access changes reviewable, and makes a failure diagnosable without granting every permission to everyone.
Frequently Asked Questions
How do I give a Rust player permission to use a plugin?
Load the plugin, copy its exact registered node, and run oxide.grant user <name|Steam64ID> <permission> in the server console or RCON. Verify the result with oxide.show user <name|Steam64ID>. A direct grant affects that player only.
How do I add someone to an Oxide group?
Create the role with oxide.group add <group>, grant its documented nodes with oxide.grant group <group> <permission>, then add the player using oxide.usergroup add <name|Steam64ID> <group>. Check membership with oxide.show group <group>.
What is the Oxide grant command?
For a user, use oxide.grant user <name|Steam64ID> <permission>. For a role, use oxide.grant group <group> <permission>. Replace every placeholder and use the exact node listed by the plugin.
Why does my Rust plugin say I do not have permission?
Check the node spelling, confirm it appears in oxide.show perms, verify the player is in the group you changed, and inspect inheritance with oxide.show group. Also make sure the command itself is being run through authenticated console or RCON access.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Do Oxide permissions exist automatically?
No. Permissions exist only when Oxide itself or an installed plugin provides and registers them. If a plugin failed to load, its nodes may be absent from oxide.show perms, and granting a guessed string will not enable the feature.
Are plugin permissions the same as Rust administrator access?
No. Server owner or moderator status controls administrative commands, while plugin nodes control capabilities checked by plugin code. An administrator can still lack a specific node, and a regular player can receive one narrowly scoped node without becoming an administrator.
How does Oxide group inheritance work?
The first group in oxide.group parent <group> <parentGroup> is the child. It inherits permissions from the second group. For example, oxide.group parent moderator default gives moderator the permissions of default, not the reverse.
How can I see who has a permission?
Run oxide.show perm <permission>. Use oxide.show user <name|Steam64ID> for one player and oxide.show group <group> for a role’s members and permissions.
Should I use the wildcard *?
Only when the role genuinely needs every permission in that scope. Prefer explicit plugin nodes for normal staff and VIP roles. Wildcards such as oxide.* can make access much broader and can hide the real cause of a permission problem.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can I run these commands in chat?
Some Oxide-supported games accept permission commands through chat, but the dependable path for Rust administration is the server console or a compatible RCON client. The issuing account still needs the required moderator or administrator access.
The Bottom Line
Use the exact node registered by the plugin, run commands from authenticated console or RCON, and prefer groups for repeatable roles. Verify with oxide.show perms, oxide.show group, oxide.show user, and oxide.show perm. Keep inheritance deliberate, avoid broad wildcards, and remove temporary administrator or test grants when the job is complete.
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.
