Maker oversight
List Maker accounts, inspect account details, and apply authorized account-management actions.
Actor guide · Administrator
Oversee maker accounts and platform security activity.
The Administrator workspace is deliberately narrow: authenticate as an administrator, manage Maker accounts, review platform security events, and end the privileged session when the task is complete.
Administrator responsibilities
Security review
Review platform-level security events across actors and resources, paying attention to failed or unexpected outcomes.
Privileged-session hygiene
Use Administrator access only for oversight, never for routine device operation, and sign out immediately afterward.
Highest-impact role. Administrator actions can affect organizational access. Verify the
target Maker and the reason for a change before confirming it.
Start an Administrator session
- Choose Administrator.Open the Administrator workspace from the app home screen.
- Sign in with an Administrator credential.Do not reuse Maker or Operator credentials as an administrative identity.
- Confirm the privileged dashboard.The authenticated workspace exposes Makers, Security events, and Sign out.
- Perform the approved task.Keep the session focused and avoid leaving the phone unattended.
- Sign out explicitly.Use the Administrator logout action as soon as the task is complete.
Manage Maker accounts
- Open Makers to retrieve the account list.
- Select the intended Maker and verify its identity and contact details.
- Use the available view, edit, activation, deactivation, or deletion action only when policy authorizes it.
- Confirm the resulting state and review the corresponding security event.
Separation of duties. Administrators govern Maker accounts. Makers maintain their device domain,
and Operators perform NFC or Bluetooth interaction. Switch accounts rather than crossing those role boundaries.
Review platform security events
Use Security events to investigate activity across the platform. Correlate the following before taking action:
| Evidence | Question to answer |
|---|---|
| Time and outcome | When did the event occur, and did the operation succeed, fail, or get denied? |
| Event type and reason | Which authentication or resource action occurred, and why was that outcome recorded? |
| Actor | Was the initiating Administrator, Maker, Operator, or system process expected? |
| Affected resource | Does the device, account, passkey, or NFC record belong to the expected organization? |
Preserve relevant event identifiers and timestamps when escalating. Never copy tokens or NFC key material into tickets or unapproved logs.
Administrator safety checklist
- Confirm the target account twice before a destructive or access-changing action.
- Use a managed phone and approved network for administrative work.
- Do not scan NFC tags or operate devices from the Administrator workspace.
- Review security events after consequential Maker account changes.
- Sign out and secure the phone when the administrative task ends.