Navigate to User Management > Groups to manage user groups and control what each group of users can do on your site.
Overview
Every user belongs to exactly one group. Groups have two layers of access control:
- Permission Level — A hierarchical role (A through F) that sets broad access based on a built-in hierarchy
- Feature Overrides — Optional per-group overrides that grant or deny specific capabilities beyond what the hierarchy allows
This two-layer system lets you fine-tune access: for example, give Moderators the ability to create bonuses (which normally requires Admin level), or prevent an Admin account from editing settings.
Permission Levels
| Level | Role | Admin Panel Access | Default Capabilities |
|---|---|---|---|
| A | Super Admin | Full | Everything, including destructive operations |
| A1 | Admin | Full | User management, finances, tables, tournaments, bots, bonuses |
| B | Moderator | Limited | User list/edit/block, messages, table viewing |
| C | Agent Manager | None | No admin panel access; agents use their own agent area |
| D | Agent | None | No admin panel access; agents use their own agent area |
| E | VIP Player | None | Special player privileges only |
| F | Regular Player | None | Basic gameplay only |
The hierarchy is strict: a higher level (closer to A) inherits everything from lower levels. An A1 Admin can do everything a B Moderator can, but not what an A Super Admin can.
Default Groups
When you first set up your site, these groups are created automatically:
| Group | Level | Purpose |
|---|---|---|
| Administrators | A | Full system access |
| Moderators | B | Support and user management |
| Players | F | Standard player accounts |
| Bots | F | Bot player accounts |
| Demo | A1 | View-only admin (write features denied via overrides) |
Additionally, the system creates internal groups on startup: super_admin (A), admin (A1), moderator (B), agent_manager (C), agent (D), vip (E), player (F).
Creating a Group
Click Create Group in the top-right corner.
- Group Name — 1 to 50 characters, letters, numbers, and underscores only (no spaces)
- Permission Level — Select the base role from the dropdown
Click Create Group to save.
Editing a Group
Click the pencil icon on any group row to change its name or permission level. Click Save Changes to apply.
Note: The server reads a user’s group permission level on every authenticated request, so a level change applies to users in the group on their next request.
Deleting a Group
Click the trash icon on a group row. A confirmation modal appears.
You cannot delete a group that has users assigned. Move all users to another group first, then delete the empty group.
Viewing Group Members
Click the people icon on any group row to open a paginated list of all users in that group. The list shows username, email, blocked status, and join date.
Managing Feature Permissions
Click the shield icon on any group row to open the Permissions modal. This lets you grant or deny individual features beyond what the permission level provides.
How It Works
Every feature has a hierarchy default — whether the group’s permission level normally grants that feature. The permissions modal shows:
- Checkmark (green) — feature is currently granted
- Dash (red) — feature is currently denied
- "override" badge — a custom override exists for this feature (different from the hierarchy default)
- "pending" badge — you have an unsaved change for this feature
- "default: allow/deny" label — what the hierarchy would give without any override
Toggling a Feature
Click the green/red indicator next to any feature to toggle it. Changes are staged as "pending" until you save.
Click Save Changes (N) to apply all pending changes. Click Cancel to discard them.
tables:manage_players and users:manage have no row in this modal, so they follow the group’s permission level.
Resetting Overrides
- Reset individual feature: Click the rotating arrow icon next to a feature to revert it to its hierarchy default
- Reset All Overrides: If the group has any overrides, a "Reset All Overrides" button appears at the bottom of the modal. This removes all custom settings and reverts the group entirely to its hierarchy defaults
Feature Reference
Features are grouped by category. The "Required Level" column shows the minimum permission level needed by default (before any overrides).
Table Management
| Feature | Required Level | What It Allows |
|---|---|---|
tables:read | B | View table list and details |
tables:create | A1 | Create new tables |
tables:edit | A1 | Edit table configuration |
tables:delete | A1 | Delete tables |
tables:pause | A1 | Pause and resume tables |
tables:debug | A1 | Access debug tools |
tables:set_cards | A | Override cards for testing |
tables:view_history | B | View hand history |
tables:manage_players | A1 | Force-remove players and force timeouts |
User Management
| Feature | Required Level | What It Allows |
|---|---|---|
users:list | B | View the user list |
users:create | A1 | Create new user accounts |
users:edit | B | Edit user profiles and balances |
users:delete | A | Delete user accounts |
users:block | B | Block and unblock users |
users:approve | B | Review verification requests |
users:verify_email | B | Manually confirm email addresses |
users:view_history | B | View user activity history |
users:manage | A1 | Force-disconnect users |
Group Management
| Feature | Required Level | What It Allows |
|---|---|---|
groups:list | B | View the groups list |
groups:create | A | Create new groups |
groups:edit | A | Edit group settings and permissions |
groups:delete | A | Delete groups |
groups:assign | A1 | Move users between groups |
System Settings
| Feature | Required Level | What It Allows |
|---|---|---|
settings:view | A1 | View server and game settings |
settings:edit | A | Modify settings |
Production Updates
| Feature | Required Level | What It Allows |
|---|---|---|
updates:view | A1 | View update status |
updates:manage | A | Queue host-level update commands |
updates:apply | A | Apply host-level updates |
Financial
| Feature | Required Level | What It Allows |
|---|---|---|
finance:view | A1 | View financial overview |
finance:transactions | A1 | View transaction records |
finance:withdrawals | A1 | View withdrawal requests |
finance:bonuses | A1 | View bonus activity |
transactions:view | A1 | View transaction list |
withdrawal:approve | A1 | Approve or reject withdrawals |
payment:view | A1 | View payment provider configuration |
payment:edit | A | Modify payment providers |
Bonuses
| Feature | Required Level | What It Allows |
|---|---|---|
bonuses:create | A1 | Create bonus campaigns |
bonuses:edit | A1 | Edit bonus campaigns |
bonuses:delete | A1 | Delete bonus campaigns |
Tournaments
| Feature | Required Level | What It Allows |
|---|---|---|
tournaments:view | B | View tournament list |
tournaments:create | A1 | Create tournaments |
tournaments:edit | A1 | Edit tournament settings |
tournaments:delete | A1 | Delete tournaments |
tournaments:manage | A1 | Start, cancel, manage running tournaments |
Bots
| Feature | Required Level | What It Allows |
|---|---|---|
bots:create | A1 | Create bot player accounts |
bots:manage | A1 | Assign bots to tables and manage them |
Messages
| Feature | Required Level | What It Allows |
|---|---|---|
messages:view | B | View the inbox and messages |
messages:send | B | Compose and send messages |
messages:delete | A1 | Delete messages |
messages:bulk | A1 | Bulk message operations |
Agents and Affiliates
| Feature | Required Level | What It Allows |
|---|---|---|
agents:view | A1 | View agent list and details |
agents:edit | A1 | Manage agents and player assignments |
affiliate-fraud:view | A1 | View affiliate data |
affiliate-fraud:edit | A1 | Manage affiliate levels and codes |
Content and Communication
| Feature | Required Level | What It Allows |
|---|---|---|
email-templates:create | A1 | Create email templates |
email-templates:edit | A1 | Edit email templates |
email-templates:delete | A1 | Delete email templates |
emails:send | A1 | Send emails to users |
pages:read | B | View CMS pages |
pages:create | A1 | Create CMS pages |
pages:edit | A1 | Edit CMS pages |
pages:delete | A1 | Delete CMS pages |
languages:read | B | View language strings |
languages:write | A1 | Edit language strings |
System and Compliance
| Feature | Required Level | What It Allows |
|---|---|---|
compliance:view | A1 | View KYC and compliance data |
compliance:edit | A1 | Manage compliance records |
circuits:view | A1 | View circuit breaker status |
circuits:reset | A | Reset circuit breakers |
admin-sessions:view | A1 | View session history |
admin-sessions:invalidate | A | Invalidate admin sessions |
archival:view | A1 | View archival configuration |
archival:edit | A | Modify archival settings |
game-scheduler:read | A1 | View scheduled games |
game-scheduler:manage | A1 | Manage game schedules |
developer:read | B | View partner info and audit logs |
developer:manage | A1 | Create, edit, and delete partners and manage API keys |
developer:settings | A | Change global developer API settings |
Common Group Configurations
View-Only Admin
Create an Admin-level (A1) group with all write features denied via overrides. This is useful for giving managers visibility without the ability to make changes.
- Create a group with permission level A1
- Open the Permissions modal
- Deny all
*:edit,*:create,*:delete, and*:managefeatures
Elevated Moderator
Create a Moderator-level (B) group with some additional capabilities:
- Create a group with permission level B
- Open the Permissions modal
- Grant
bonuses:createandbonuses:editto allow the moderator to manage promotional campaigns
Cashier Role
Create a group with level B but grant specific financial permissions:
- Create a group with permission level B
- Open the Permissions modal
- Grant
withdrawal:approve,finance:view,finance:withdrawals, andtransactions:view
Important Behaviors
Session invalidation: When a user is moved to a different group, all their active sessions and tokens are immediately revoked. They must log in again to receive their new permissions.
Cascade delete: Deleting a group removes all its feature overrides. Users cannot be in a deleted group.
Delete guard: A group with users assigned cannot be deleted. The system shows an error with the user count.
Override caching: Feature overrides are cached in memory for performance. The cache is cleared automatically whenever you save changes in the Permissions modal.
Required Permissions
| Action | Required Permission |
|---|---|
| View groups | groups:list |
| Create groups | groups:create |
| Edit groups and permissions | groups:edit |
| Delete groups | groups:delete |
| Assign users to groups | groups:assign |