OpenPoly logo
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.

GroupPagePathRequired scopePurpose
OverviewOverview/authenticated sessionMetrics for users, trade fees, 24h trade fees, and visible active markets.
OperationsUsers/usersusers:readOperator-linked Mini App users.
OperationsTrades/tradestrades:readOrders, generated trade fees, and operator fee share.
OperationsResolutions/resolutionsredemptions:readResolved market exposure and payout liability.
OperationsBalance Ops/balance-operationsbalance_operations:readWallet debits, credits, reversals, retries, balance-after evidence, and exports.
PolyflightOverview/polyflightpolyflight:readNative activity, signed position, and outstanding liabilities.
PolyflightFlights/polyflight/flightspolyflight:readShared flights with this operator's participation.
PolyflightTickets/polyflight/ticketspolyflight:read, polyflight_terms:readNative tickets, captured terms, result, and payment state.
PolyflightBalance operations/polyflight/balance-operationspolyflight:read, balance_operations:readPolyflight wallet effects and evidence.
PolyflightSettlement reports/polyflight/settlement-reportspolyflight_settlements:readSigned statements, liabilities, exports, and payments.
PolyflightTerms/polyflight/termspolyflight_terms:readRead-only current, scheduled, and historical terms.
API PlaygroundSession through Staffs/api-playground/{group}matching request scopeAllowlisted Operator API workspace with inherited staff auth, confirmations, and response inspection.
OperationsMarkets/marketsmarkets:readMarket visibility, YES percentage, trading cutoff, and operator 24h volume.
SimulatorSimulator/simulatorsimulator:readStaging-only launch drill page for simulator users.
SimulatorSimulator Users/simulator/userssimulator:readStaging-only simulator user and balance management.
IntegrationsWallet Adapter/settings/wallet-adapterwallet_adapter:readREST v1 wallet adapter config and validation tests.
IntegrationsAPI Keys/settings/api-keysapi_keys:readOperator API key creation, rotation, and revocation.
IntegrationsStaffs/settings/staffsstaffs:readHuman dashboard staff accounts and dashboard permissions.
IntegrationsCallback Settings/settings/callbackswebhooks:readWebhook endpoint configuration and recent delivery actions.
IntegrationsWebhook Deliveries/webhooks-deliverieswebhooks:readDelivery audit trail and replay workflow.

Suggested setup order

  1. confirm staff access and assign least-privilege staff scopes
  2. create backend API keys for launch/reporting workloads
  3. configure and test REST v1 wallet adapter
  4. configure webhook endpoint, events, attempts, timeout, and secret
  5. if enabled, verify Polyflight terms/timezone and explicitly assign its read scopes
  6. review market visibility before public rollout
  7. run staging simulator, wallet adapter, and webhook drills
  8. verify Opinion and Polyflight operation/event/report evidence before requesting production approval

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.
  • Polyflight operator pages are read-only; only Polynion administration can change terms, finalize/pay statements, or resolve ambiguous operations.
  • 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
Copyright © 2026