Dashboard
Overview
Operator dashboard surfaces and their purpose.
Overview
Operator Dashboard is the control plane for Mini App operations.
Current navigation
The current dashboard menu is registered in apps/mini-app-operator-dashboard/app/utils/operator-page-registry.ts.
| Group | Page | Path | Required scope | Purpose |
|---|---|---|---|---|
| Overview | Overview | / | authenticated session | Metrics for users, trade fees, 24h trade fees, and visible active markets. |
| Operations | Users | /users | users:read | Operator-linked Mini App users. |
| Operations | Trades | /trades | trades:read | Orders, generated trade fees, and operator fee share. |
| Operations | Resolutions | /resolutions | redemptions:read | Resolved market exposure and payout liability. |
| Operations | Balance Ops | /balance-operations | balance_operations:read | Wallet debits, credits, reversals, retries, balance-after evidence, and exports. |
| API Playground | Session through Staffs | /api-playground/{group} | matching request scope | Allowlisted Operator API workspace with inherited staff auth, confirmations, and response inspection. |
| Operations | Markets | /markets | markets:read | Market visibility, YES percentage, trading cutoff, and operator 24h volume. |
| Simulator | Simulator | /simulator | simulator:read | Staging-only launch drill page for simulator users. |
| Simulator | Simulator Users | /simulator/users | simulator:read | Staging-only simulator user and balance management. |
| Integrations | Wallet Adapter | /settings/wallet-adapter | wallet_adapter:read | REST v1 wallet adapter config and validation tests. |
| Integrations | API Keys | /settings/api-keys | api_keys:read | Operator API key creation, rotation, and revocation. |
| Integrations | Staffs | /settings/staffs | staffs:read | Human dashboard staff accounts and dashboard permissions. |
| Integrations | Callback Settings | /settings/callbacks | webhooks:read | Webhook endpoint configuration and recent delivery actions. |
| Integrations | Webhook Deliveries | /webhooks-deliveries | webhooks:read | Delivery audit trail and replay workflow. |
Suggested setup order
- confirm staff access and assign least-privilege staff scopes
- create backend API keys for launch/reporting workloads
- configure and test REST v1 wallet adapter
- configure webhook endpoint, events, attempts, timeout, and secret
- review market visibility before public rollout
- run staging simulator, wallet adapter, and webhook drills
- verify trade, balance operation, resolution, and webhook delivery evidence before production
What dashboard changes do
- API key changes affect operator API access immediately.
- Staff changes affect human dashboard access and revoke changed staff sessions.
- Wallet adapter changes affect balance reads and wallet mutation callbacks.
- Webhook endpoint changes affect future deliveries; replay sends existing callback objects again.
- Market visibility changes affect which markets appear to operator users.
- Simulator changes affect staging/local simulator-tagged users only.
What dashboard does not change
- public operator API path structure
- wallet adapter path structure
- webhook event names
- shared integration contract described in these docs
- production users when a simulator-only user is edited
Related pages
- users:
/docs/dashboard/users - trades:
/docs/dashboard/trades - resolutions:
/docs/dashboard/resolutions - balance operations:
/docs/dashboard/balance-operations - markets:
/docs/dashboard/market-visibility - API keys:
/docs/dashboard/api-keys - wallet adapter settings:
/docs/dashboard/wallet-adapter-settings - webhook endpoints:
/docs/dashboard/webhook-endpoints - webhook deliveries:
/docs/dashboard/webhook-deliveries - staffs:
/docs/dashboard/staffs - simulator:
/docs/dashboard/simulator - API Playground:
/docs/dashboard/api-playground