Dashboard overview
Operator workspaces under /dashboard/platform, two-factor requirement, and dual control.
Operator pages are app/dashboard/(admin)/platform/<route>/page.tsx, backed by features/platform/<slice>. Most actions need operator two-factor assurance (valid 12 hours after a TOTP check) and the right role flag. Sensitive changes are requested by one operator and decided by another.
| Workspace | Page |
|---|---|
| Control room | /dashboard/platform |
| Catalog | Catalog |
| Trading and risk | Trading, Risk |
| Wagers | Wagers |
| Results to settlement | Results and grading, Settlement |
| Players | Customers, Compliance, Responsible gaming, Support |
| Money | Finance, Licences and payments, Promotions |
| Operations | Integrations, Recovery and incidents, Reports |
| Governance | Configuration, Settings, Roles and approvals, Audit |
The Control room shows today's queues, exceptions, exposure, latest wagers, and shortcuts. Lists without a dedicated page appear on the generic /dashboard/<list-key> pages, mostly read-only.
Dual control
A request writes an ApprovalRequest with the reviewed payload and a payload hash; it expires after 24 hours. A different operator with canApproveSensitiveActions decides it in /dashboard/platform/approvals (decideSensitiveApproval). The requester cannot approve their own request (DUAL_CONTROL_REQUIRED). The apply mutation checks the approval, hash, and expiry before changing anything.
Pairs: settings, roles, grants, revocations, operator admission, legal entities, jurisdiction activation, brands, currencies, locales, house rules, feature flags, promotions, webhook endpoints, trader overrides, correlation rules, tax rules, ledger adjustments, resettlements, cash-out corrections, dispute resolutions, retention executions, data exports.