Skip to main content

Groups & access rights

This page explains how admins manage groups, group members, and group access rights.

Navigation path:

  • Server Admin → Groups

Access requirements​

  • groups.view to open the list
  • groups.create to create groups
  • groups.edit to update groups and members
  • groups.delete to remove groups
  • groups.edit_access_rights to update access rights

Groups overview​

The overview lists all groups and their player counts.

For groups that are configured as server default groups, the player count shows the effective member count for that server. This means every linked player is included there even if no player was assigned to the group directly.

Use Add group to create a new one or open an existing group to manage it.

Group settings​

Inside a group, you can:

  • rename the group
  • manage which other groups' places can be managed (place delegation)

Access rights tab​

Use this tab to grant rights to all group members at once.

If you need to change a single player only, use direct user rights in the player detail view instead. For the full access model and naming conventions, see Access control.

Common ticket setup:

  • Use player.tickets.view for player-facing ticket access in the shop.
  • Use admin.tickets.view for staff who should open the admin ticket queue without changing tickets.
  • On servers using support levels, also grant the admin.tickets.level_<id> right for every level the group should see. Without one, the group's queue stays empty.
  • Add admin.tickets.reply, admin.tickets.internal_message, admin.tickets.assign, and admin.tickets.change_status only to support roles that should actively work tickets.
  • Add admin.tickets.change_level for staff who may escalate a ticket to another support level.
  • Keep admin.tickets.manage_levels and admin.tickets.manage_categories with the groups that shape the setup rather than work it: the first creates and reorders the support levels themselves, the second edits the request types and their intake forms and publishes their Discord panels. Neither is needed to handle tickets.

Settings for moderators​

Below Edit all settings in the settings block, Set individually opens every settings area and every single setting as its own right — searchable, with filters for allowed, denied and deviating entries. Each area has its own switch, each setting inside it too; an entry on Neutral follows the area, and the area follows Edit all settings. A badge shows what a neutral entry currently inherits.

Example: moderators may switch the whitelist on and off, nothing else. Leave Edit all settings and the Whitelist & Accounts area on Neutral and allow only Whitelist enabled.

Default groups is the exception: it decides which rights every player gets, so it cannot be granted on its own and only changes with Edit all settings.

What a group with single settings sees:

  • Without View all settings, the settings page shows exactly the settings it may change; with it, every setting, but only the allowed ones can be changed.
  • Discord /server shows only the switches it may flip.
  • The AI Companion and scheduled tasks of the type "Change server settings" can change exactly the same settings — a scheduled task cannot be saved with a setting its author may not change.

Players tab​

Add or remove members from the group. Membership changes apply immediately to access checks.

Places tab (delegated place management)​

If enabled, this tab lets you create and manage places on behalf of groups you are allowed to manage. This is useful for hierarchical staff workflows where one group manages another group's coordinates.