Operator guideEN

Staff / View

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

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 page does

This page is the read-oriented workspace for one CRM admin account. It is used when an operator needs to confirm who the account belongs to, which role and group it carries, and which permissions are actually stored for that record.

The page title is built from the stored role name and the staff member's first and last name. The page loads one admin-detail payload for the selected staff id and then switches between local tabs without making a second tab-specific backend request.

Tabs on this page

Overview

Shows the core identity and access fields for the selected admin user.

Visible fields are First Name, Last Name, Email, Username, Role, and Group. Missing values render as N/A.

Permissions

Shows the permission matrix as categories and readable permission labels so operators can inspect the real stored access set instead of relying only on the role name.

Important caveats

  • The page is powered by the same backend detail payload that the edit form uses.
  • The root superadmin path can display a special full-permission set from the backend detail service.
  • Use this page for inspection, not for direct mutation. The current view page does not expose a dedicated Edit or Back button; edits happen through the separate form surface.
  • If the detail payload or permission row is missing, the UI can show a loading or "No permission data available" state instead of the field cards.
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.

Calculations4 topicsOpen details

Route detail selection

Staff View always represents one selected CRM admin account.

Inputs
selected staff id, admin detail payload
Transform
The page converts the selected staff id from the route and requests the matching admin detail payload.
Caveats
If the route id is invalid, missing, or not visible to the current operator, the page cannot render a trusted staff detail.

Local tab switching

Switching between Overview and Permissions changes what is displayed but does not refresh or mutate staff data.

Inputs
Overview tab, Permissions tab, loaded admin detail payload
Transform
Tab changes update local UI state and reuse the already loaded detail payload.
Caveats
The Permissions tab can show an empty-state message when the loaded detail payload lacks a permission row.

Permission label rendering

Permission labels are display aliases; the stored permission code remains the source of truth.

Inputs
stored permission category, stored permission code, permission display map
Transform
The Permissions tab renders each stored code with a known display label, or falls back to the raw stored code when no alias exists.
Caveats
The view page does not enforce edit rules or read-before-write gating; it only displays stored permissions.

Root superadmin permission override

The root superadmin view can show the full backend-defined permission set even when stored child-account permission rows differ.

Inputs
loaded staff id, loaded parent id, backend root-superadmin rule
Transform
Backend replaces the permission object with the full permission template when the selected staff record is the original root superadmin.
Caveats
This is backend detail-read behavior, not a Staff View-specific calculation.
Fields9 topicsOpen details

First Name

First name stored for the admin user.

Group
overview
Data Type
string
Fallback
N/A

Last Name

Last name stored for the admin user.

Group
overview
Data Type
string
Fallback
N/A

Email

Login email for the admin account.

Group
overview
Data Type
string
Fallback
N/A

Username

Stored CRM username for this admin account.

Group
overview
Data Type
string
Fallback
N/A

Role

Backend role associated with the record.

Group
overview
Data Type
enum
Fallback
N/A

Group

Operational group attached to the admin account.

Group
overview
Data Type
string
Fallback
N/A

Permission Category

Permission group rendered as one card in the Permissions tab.

Group
permissions
Data Type
string

Permission Codes

Stored permission codes for the category.

Group
permissions
Data Type
string-list

Permission Label

Human-readable label shown for a stored permission code, with the raw code used as fallback when no display alias exists.

Group
permissions
Data Type
display-label
Examples
C: Create | R: Read | U: Update | T: Toggle Status | D: Delete | SR: Special Read | AB: Additional | AA: Add Adjustment | TE: Test Edit | Approve: Approve | Reject: Reject
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 / Permissions

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

Bonuses / View

Read-only bonus detail screen used to inspect one reusable bonus definition before editing it.