Operator guideEN

Staff / Permissions

Read-only explanation of the permission matrix shown inside the staff view workspace.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this relation shows

This surface documents the permission matrix shown on the Permissions tab of the staff view page. Operators use it to verify the effective access pattern for one admin account.

How to interpret it

  • Permissions are grouped by category cards.
  • Each category shows one or more permission labels derived from stored permission codes.
  • Unknown permission codes display as the raw code.
  • The matrix is read-only in the view screen. Any change requires the edit form and a backend update.

Important caveats

  • The permission matrix can reveal more detail than the visible role label.
  • The root superadmin path can resolve to a full backend-defined permission set.
  • The current permissions tab does not render an inline Edit button; use the Staff edit form from the normal staff workflow when permissions need to change.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Fields5 topicsOpen details

Permission Category

Named permission group rendered as a category card.

Group
permissions
Data Type
string

Permission Codes

Stored permission codes for the category, rendered as the effective access set.

Group
permissions
Data Type
string-list

Permission Label

Human-readable display label shown for a stored permission code.

Group
permissions
Data Type
display-label
Examples
C: Create | R: Read | U: Update | T: Toggle Status | D: Delete | Issue: Issue | SR: Special Read | AB: Additional | AA: Add Adjustment | TE: Test Edit | Approve: Approve | Reject: Reject
Caveats
Unknown permission codes are displayed as the raw stored code.

Check icon

Indicates that the listed permission code exists in the stored category array.

Group
permissions
Data Type
visual-indicator

Role Context

Role context that helps explain why the permission matrix looks the way it does.

Group
context
Data Type
enum
More help

Related pages

Backoffice / Staff

Operator documentation for backoffice administrator accounts, including list, create or edit, read-only inspection, and permission review.

Staff / Detail Model

Shared detail payload for one admin account, used by both the read-only view page and the edit form.

Staff / Form

Combined create and edit workflow for one backoffice administrator account, including role, group, parent-admin, and permission matrix rules.

Staff / List

Staff inventory with search, create navigation, view or edit entrypoints, and a restricted demo-admin action.

Staff / View

Read-oriented staff workspace with overview fields and a dedicated permissions tab.

Challenges / Permissions

Rule-management surface for challenge eligibility constraints, including tags, loyalty level, ranges, bonus participation, and game categories.