This guide explains how to grant admin or moderator permissions on a Rust server, whether it’s your own dedicated server or a rented one. You’ll learn the exact commands and configuration changes needed to promote players, and what each permission level allows.
What You’ll Need
- Access to the server console (either through your hosting panel, RCON, or the in-game console if you’re the owner).
- The Steam ID (17-digit number) of the player you want to promote. You can find this by asking the player or using a service like SteamID.io.
- For the oxide/plugins method: Oxide (uMod) installed on your server.
Step-by-Step
- Identify the server type. Rust servers can be either vanilla (no plugins) or modded (using Oxide/uMod). The method differs slightly.
- For vanilla servers: Use the
owneridcommand to add a player as the server owner (full admin). Open the server console and type:ownerid <SteamID> <name>(replace <SteamID> with the player’s Steam ID and <name> with their in-game name). This grants all permissions, including the ability to use all admin commands and access the console. - For modded servers (Oxide): Use the
oxide.usergroup addcommand. In the console, type:oxide.usergroup add <SteamID> adminto add to the admin group, oroxide.usergroup add <SteamID> moderatorfor the moderator group. The admin group typically has full permissions, while moderator has a subset defined by the server owner. - Alternatively, use the
moderatoridcommand on vanilla servers. This grants moderator-level permissions (e.g., kick, ban, but not all admin commands). Syntax:moderatorid <SteamID> <name>. - If you’re using a hosting panel (like Gamepanel or TCAdmin): Look for a “Players” or “Permissions” section. There, you can often add players by Steam ID and assign a role (Owner, Admin, Moderator) via a dropdown menu.
- For in-game (if you are the server owner): Open the console with F1 and type the same commands as above. You must have
server.secureset to true for these to work reliably. - Verify the permissions: Ask the player to reconnect. They should now have access to the granted commands. To test, have them type
statusin the console – they should see an “admin” or “moderator” tag next to their name.
Common Mistakes
- Using the wrong Steam ID format. Ensure it’s the 17-digit SteamID64, not the custom URL or the older SteamID 32-bit format.
- Typing commands in the wrong console. The commands must go into the server console (or in-game console if you’re the owner), not the client console (the one that opens with ~).
- Forgetting to reload the oxide config. After adding a user to a group, sometimes you need to run
oxide.reloador restart the server for changes to take effect. - Confusing
owneridwithmoderatorid. Ownerid gives full control, including the ability to change server settings. Moderatorid only gives moderation tools.
Tips
- Use groups for easier management. Instead of assigning permissions to each player individually, create groups (e.g., “admin”, “moderator”) and assign players to those groups. This makes it easy to change permissions for all members at once.
- Set up permissions for plugins. If you use plugins like BetterChat or AdminPanel, you may need to grant additional permissions via
oxide.grant user <SteamID> <permission>. - Keep a record of who has admin. This helps with accountability and troubleshooting.
- Use the
oxide.groupcommand to see current group memberships. This helps verify that the addition was successful.
Troubleshooting
- The player doesn’t have admin after adding. Check that the Steam ID is correct. Ask the player to fully restart their game. If using Oxide, run
oxide.reloador restart the server. - Commands are not working. Ensure that the player is typing the commands in the correct console (F1 for in-game). Also, some commands require the player to be in the server for the command to work.
- You can’t access the server console. If you’re renting, use the hosting panel’s console. If you’re self-hosting, check that RCON is enabled and you’re connecting to the correct port.
- Oxide commands not recognized. Make sure Oxide is installed and up-to-date. Type
oxide.versionin the console to verify.
Frequently Asked Questions
Q: Can I give admin rights to a player who is not online?
A: Yes, you can add them via the console using their Steam ID, even if they are offline.
Q: What’s the difference between owner and admin?
A: Owner (ownerid) has all permissions, including changing the server’s config files and saving/loading maps. Admin (oxide admin group) typically has all in-game commands but not file-level access.
Q: How do I remove admin rights?
A: Use oxide.usergroup remove <SteamID> admin for Oxide, or ownerid <SteamID> <name> 0 to remove owner status (the 0 at the end removes).
Q: Do I need to restart the server after adding a moderator?
A: Usually not, but if the player doesn’t get permissions immediately, a restart or oxide.reload can help.
Q: Can I give a player only specific permissions, like just kick?
A: Yes, with Oxide you can create custom groups and assign specific permissions using oxide.grant user <SteamID> <permission>.
Q: What if I lose my own admin rights?
A: If you’re the server owner, you can use the RCON console to re-add yourself. If you don’t have RCON, you may need to edit the server’s users.cfg file directly via FTP.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- Credential Manager: Seamless Sign-In Explained
- API Governance for Public Data: What Growing Portfolios Need
- Enterprise AI Hidden Cost: Data Architecture ROI