> ## Documentation Index
> Fetch the complete documentation index at: https://pure.saauf.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Set Up Roles and Staff Access Permissions in Trace
> Create and edit staff roles in Trace, assign permissions, link Roblox Group ranks, and control what each team member can see and do.
Roles are how Trace determines what each member of your team can see and do inside the admin panel. Every staff member is assigned a role, and every role carries a permission set and a numeric level that defines where it sits in your moderation hierarchy. Setting roles up correctly from the start keeps your team organized and prevents staff members from accessing tools beyond their responsibility.
## Role Fundamentals
### Built-in Roles
Two roles are permanent and cannot be removed or modified:
| Role | Level | Notes |
| -------------------- | ----- | ------------------------------------------------------------------------------------------------ |
| **Experience Owner** | 1000 | Full access to everything. Automatically granted to the Roblox account that owns the experience. |
| **Player** | 0 | The baseline role assigned to all players who are not staff. |
### Default Staff Roles
Trace ships with the following staff roles preconfigured. You can edit or remove any of these to match your team structure:
| Role | Level |
| ---------------- | ----- |
| Admin | 400 |
| Manager | 300 |
| Senior Moderator | 200 |
| Moderator | 100 |
| Reviewer | 50 |
Role levels are arbitrary integers - what matters is their relationship to each other. A role at level 200 can manage any role below level 200 and cannot touch any role at level 200 or above.
Never assign a staff member a role with a level equal to or higher than your own. If a staff member's role reaches your level, they gain the ability to modify your account's role assignment and permissions. Only the Experience Owner (level 1000) is immune to this, as no assignable role can reach level 1000.
## Creating a New Role
Inside the Trace admin panel, navigate to **Settings** and select the **Roles** category. You must be the Experience Owner to create, edit, or delete roles.
Click the **New Role** button. A creation form opens on the right side of the panel.
Enter a descriptive name for the role (for example, `Junior Moderator`) and assign a numeric level. The level must be lower than your own role level and should sit logically between any existing roles you want this role to rank between.
Toggle on the permission groups this role should have access to. See [Permission Groups](#permission-groups) below for a breakdown of what each group controls.
Click **Save**. The role is now available to assign to staff members.
## Adding a Staff Member
To grant a player staff access, assign their **Roblox UserId** to a role in **Settings → Roles**. Open the role you want to assign them to, navigate to the Members section, and enter their UserId. They will receive that role's permissions the next time they open the admin panel.
## Roblox Group Integration
If your team is managed through a Roblox Group, you can automate role assignment by linking a Trace role to a Group rank.
In the role editor, enable **Group Integration** and provide:
* **Group ID** - the numeric ID of your Roblox Group
* **Minimum Rank** - the minimum group rank value required to receive this Trace role
Any group member at or above the specified rank is automatically granted the linked Trace role when they open the admin panel. You do not need to add them individually by UserId.
You can combine manual UserId assignments and Group integration on the same role. Members added by UserId always have the role regardless of their group rank.
## Permission Groups
Each role's access is controlled by toggling permission groups on or off. The available groups are:
Controls whether the role can open and use the Trace admin panel at all. Disable this to create roles that exist in the hierarchy for data purposes but cannot access the panel UI.
Access to the review queue - moderation cases flagged for a second opinion before action is taken.
Access to audit logs, moderation history, and player records. Allows viewing past actions taken by all staff members visible to this role.
Access to Trace Chat (internal staff messaging) and announcement tools.
Access to the player-submitted reports queue - view, claim, and resolve reports.
Access to Server Management tools - view live servers, push announcements, and perform server-level actions.
The most granular permission group. Grants access to per-player moderation tools with individual sub-controls:
* Inspect player profiles
* Issue warnings
* Kick players
* Issue mutes
* Issue bans
* Unban players
* Manage player inventory flags
Enable only the sub-controls appropriate for the role's responsibilities. For example, a Reviewer role might have Inspect and view-only access, while a Senior Moderator has ban and unban rights.
Access to high-level administrative tools including configuration management. Typically reserved for Admin-level roles and above.
## Hierarchy Enforcement
Trace enforces role hierarchy automatically - staff members can only take moderation actions on players and roles that sit **strictly below** their own role level. This means:
* A Moderator (level 100) cannot kick, warn, or ban a Senior Moderator (level 200).
* A Manager (level 300) cannot edit the Admin role (level 400) or assign anyone to it.
* Any role action targeting a user at an equal or higher level is blocked at the panel level.
Role changes take effect for a staff member on their **next panel session** or after a server restart. If you update a staff member's role and need it to apply immediately, ask them to close and reopen the admin panel.