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 tickets.view for player-facing ticket access in the shop.
  • Use tickets.admin_view for staff who should open the admin ticket queue without changing tickets.
  • Add tickets.reply, tickets.internal_message, tickets.assign, and tickets.change_status only to support roles that should actively work tickets.

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.