> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Configure Admin & Moderator Ranks in Rust

> Master the Rust authentication levels to delegate power. Learn how to securely grant administrative access, flight, and management tools to your staff.

## Establishing Administrative Authority

Rust uses a three-tiered technical authentication system to manage server access and executive authority. Granting administrative powers is essential for moderators who need to use specialized tools such as **Noclip (flight)**, item spawning, and invisible spectating to identify and neutralize cheaters. Correctly configuring these ranks ensures that your staff team has the appropriate tools to maintain community order while protecting the server's core variables from unauthorized modification.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Beginner
  </Card>

  <Card title="Time" icon="clock">
    5 Minutes
  </Card>
</CardGroup>

***

## Technical Authentication Tiers

The Rust engine recognizes three distinct "Auth Levels" that dictate a user's command access.

* **Level 0 (Player):** Standard participant status. No access to administrative or developer commands.
* **Level 1 (Moderator):** Access to tactical moderation commands including `/kick`, `/ban`, and `/mute`. Moderators typically **cannot** spawn items or use developer cheats by default.
* **Level 2 (Owner):** Absolute authority. Access to all server variables, unrestricted item spawning, and administrative noclip.

***

## Authorization Workflow

The most secure method for assigning ranks is using the **Web RCON** console within your FREAKHOSTING dashboard.

<Steps>
  <Step title="Retrieve SteamID64">
    Obtain the player's 17-digit numerical identifier (e.g., `76561198000000000`). You can retrieve this by pasting their profile URL into [SteamID.io](https://steamid.io).
  </Step>

  <Step title="Execute Auth Command">
    In your server console, input the appropriate command:

    * **For Owners:** `ownerid <SteamID> "DescriptiveName"`
    * **For Moderators:** `moderatorid <SteamID> "DescriptiveName"`
  </Step>

  <Step title="Commit Permission Registry">
    **Critical:** You must execute the command **`server.writecfg`** immediately after. If you neglect this, the rank will only exist in temporary memory and will be lost upon the next restart.
  </Step>

  <Step title="Initialize Status">
    The player must disconnect and reconnect to the server for the new administrative flags to be recognized by the game client.
  </Step>
</Steps>

***

## Strategic Administration Best Practices

<AccordionGroup>
  <Accordion title="The Separate Account Protocol">
    To maintain community trust, we strongly recommend that administrators who intend to participate in standard gameplay use a **separate "Player" account**. If players observe an administrator building or raiding while using their staff account, it frequently triggers accusations of "Admin Abuse," potentially damaging your server's reputation for fairness.
  </Accordion>

  <Accordion title="Invisible Spectating">
    Authorized staff can enter a "Spectator" state by using the console command `spectate`. This allows you to observe suspicious players from their perspective without manifesting an in-game character model, providing an essential tool for identifying sophisticated "closet" cheaters.
  </Accordion>
</AccordionGroup>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to get a new server? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** January 2026 | **Rust:** Staff hierarchy verified.
</div>
