Operator guideEN

Staff / Detail Model

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

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 surface represents

Staff does not expose a separate generic detail page. Instead, several staff workflows rely on the same backend detail payload:

  • Staff View uses it to render the read-only Overview and Permissions tabs.
  • Staff Edit uses it to prefill editable identity, group, and permission values.
  • Staff Create uses selected parent-admin detail reads when a Support account needs permission seeding.
  • The staff list shell also reads current-operator detail to decide whether some staff actions should be visible.

Why this matters

  • When operators see one set of fields in the read-only page and another in the edit form, they are still looking at the same underlying admin detail source.
  • Role, group, identity fields, and permission data should be interpreted as one shared record model.
  • If the detail payload is wrong, both the view and edit experiences can be affected.
  • Non-root operators can be scoped by backend parent/current-admin rules when requesting another staff record.
  • Root-superadmin detail can resolve to a backend-defined full permission set.
  • Root-level detail reads can include extra operational metadata that Staff View and Staff Form do not render as staff fields.
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.

Calculations5 topicsOpen details

Current versus selected staff detail

The same detail endpoint can explain the current operator, a Staff View row, a Staff Edit row, or a Support parent-admin permission source.

Inputs
current operator session, optional selected staff id
Transform
Without a selected staff id, the detail route resolves the current operator; with a selected staff id, it resolves that staff record when backend visibility rules allow it.
Caveats
Consumers must interpret the payload in context; current-operator detail and selected-staff detail can be used for different UI decisions.

Backend visibility scope

Staff detail can fail to load when the selected staff record is outside the operator's visible staff hierarchy.

Inputs
requesting admin id, requesting admin role, selected staff id, selected staff parent id
Transform
For non-root operators requesting a selected staff id, backend adds a current-admin or child-admin visibility constraint before loading the staff record.
Caveats
This is backend read scoping, not a frontend filter.

Root superadmin permission override

Root-superadmin detail can show the complete backend-defined permission set even if normal staff rows depend on stored permission JSON.

Inputs
selected staff id, selected staff parent id, backend root-superadmin rule
Transform
Backend replaces the permission object with the full permission template when the loaded staff record is the original root superadmin.
Caveats
This is detail-read behavior shared by all consumers of the admin-detail payload.

Personal full-superadmin state

Some personal staff accounts can unlock legacy Super Admin navigation without changing auth tokens or route paths.

Inputs
staff group, role id, active flag, permission payload, workspace contract
Transform
Workspace contracts define selected personal CRM admin accounts as full-superadmin-capable when backend data grants Super Admin role state, `group='superadmin'`, active status, and full permission JSON.
Caveats
Staff Detail only documents the shared payload; navigation consumers decide how to use the full-superadmin state.

Root-level operational metadata

Staff View and Staff Form should be read as staff-account surfaces; they do not expose extra root-only metadata as staff fields.

Inputs
requesting admin role, backend detail service
Transform
Root-level backend detail reads can attach extra operational metadata, while removing password before returning the staff detail payload.
Caveats
Secret values must never be copied into authored docs or public docs output.
Fields17 topicsOpen details

Staff ID

Internal record ID reused across staff view and edit flows.

Group
identity
Data Type
integer

First Name

Shared first-name value used by Staff View and Staff Edit.

Group
identity
Data Type
string

Last Name

Shared last-name value used by Staff View and Staff Edit.

Group
identity
Data Type
string

Email

Shared login email value for the admin account.

Group
identity
Data Type
string

Username

Shared CRM username value for the admin account.

Group
identity
Data Type
string

Is Active

Active-state flag on the staff account. It is part of the shared detail payload even when a consumer surface does not render it directly.

Group
identity
Data Type
boolean

Parent ID

Parent-admin link used by backend scoping and support hierarchy logic.

Group
hierarchy
Data Type
integer

Parent Type

Backend parent type associated with the selected staff record.

Group
hierarchy
Data Type
string

Role

Role value used to interpret access tier and edit restrictions.

Group
access
Data Type
enum

Role ID

Numeric role id used by frontend and backend role-level checks.

Group
access
Data Type
integer

Role Level

Role hierarchy level used by staff action visibility and superadmin access logic.

Group
access
Data Type
integer

Group

Group value used on both inspection and edit surfaces.

Group
access
Data Type
string
Caveats
Workspace contracts document `group='superadmin'` as part of personal full-superadmin access semantics for selected CRM admin accounts.

Permission Payload

Stored permission matrix behind the permissions tab and edit form.

Group
permissions
Data Type
object
Caveats
The original root-superadmin record can receive a backend-defined full permission template during the detail read.

Permission Row ID

Internal id of the staff permission row linked to the selected staff account.

Group
permissions
Data Type
integer

Created At

Timestamp when the staff account was created.

Group
audit
Data Type
datetime

Updated At

Timestamp when the staff account was last updated.

Group
audit
Data Type
datetime

Hashed ID

Optional hashed identifier included by the backend model. It is not a primary Staff View field.

Group
technical
Data Type
string
More help

Related pages

Backoffice / Staff

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

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.

Staff / View

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

Activity Tag Rules / Detail

Rule inspection page with stored identity, conditions, timestamps, impact estimate, run action, delete action, and recent application history.