Groups

A group is an in-game player role: the rank a player belongs to (e.g. Admin, Moderator, VIP, Player). Groups are the unit you grant permissions to, and they show up wherever a player's identity is rendered (chat, scoreboard, name plates).

Groups are per-environment. Each of your three environments has its own set of groups — though Master and Default always exist in every env.

System groups

Two groups are created automatically in every environment and cannot be deleted:

Group	Slug	Role
Master	`master`	Super-admin. Implicitly holds every permission, including ones declared by addons installed in the future. Cannot be modified.
Default	`default`	The fallback group every new player lands in. Acts as the floor — anything you want every player to have, grant to Default.

You can change their display name and color, but their slug, kind, and priority are locked.

Master is the bypass. Anyone in the Master group ignores permission checks entirely — there are no rows for Master in the permissions table because it doesn't need any. Use it sparingly and only for trusted operators.

Custom groups

Beyond the two system groups, you create as many custom groups as you need (Admin, Moderator, VIP, etc.).

Each custom group has:

Field	What it is
Name	Display name (e.g. "Moderator").
Slug	URL-safe identifier (e.g. `moderator`). Auto-generated from name, editable at creation.
Color	Hex color used for badges and chat tags.
Priority	Integer between 1 and 999 — controls ordering and group precedence in the game UI.

The priority scale

1000  ─── Master    (locked)
 999  ─┐
       │  custom range
   1  ─┘
   0  ─── Default   (locked)

0 is reserved for Default — your custom groups can't have priority 0.
1000 is reserved for Master — your custom groups can't reach it.
Anywhere between 1 and 999 is yours. A common convention:
- 100–299 → trusted players (VIP, donator tiers)
- 300–599 → moderation team (Trial Mod, Mod, Senior Mod)
- 600–999 → admin team (Admin, Senior Admin, Head Admin)

Higher priority groups display above lower ones in lists, and beat them in ties for promotion / override scenarios in-game.

Create a custom group

Open your project → Environments → pick the env → Groups tab.
Click New group.
Fill in name, slug, color, and priority.
Click Create.

The group appears in the list and is immediately available in the Permissions tab as a grant target.

Edit a group

Click any row to edit it:

System groups — only name and color are editable.
Custom groups — name, slug, color, priority all editable.

Changes apply live to every server in this environment.

Delete a custom group

Click the trash icon on the row and confirm. Deleting a group also revokes every permission previously granted to it — those rows are cascade-deleted from the permissions table.

System groups (Master, Default) cannot be deleted.

Inheritance and merging

Groups follow the environment inheritance chain, but unlike variables they don't fall back to the parent — they're materialized per-environment. If you create a "VIP" group in Production, it doesn't auto-appear in Staging; you'd see it as an addition in the Changes view and can merge it across with one click.

Gamemode switch

When you switch a project's gamemode, all custom groups in every environment are deleted. Master and Default are preserved (since the new gamemode also expects them).

Next steps

Permissions — grant capabilities to the groups you just created
Changes — propagate new groups from one env to another

Groups

On this page