OpenPoly logo
Dashboard

Overview

Operator dashboard surfaces and their purpose.

Overview

Operator Dashboard is the control plane for Mini App operations.

Current navigation

Menus are filtered by the signed-in staff member's scopes and environment. A role badge such as Operator Admin is not a substitute for the required grants. API keys are for backend requests, not dashboard sign-in.

GroupPagePathRequired scopePurpose
OverviewOverview/authenticated sessionMetrics for users, trade fees, 24h trade fees, and visible active markets.
SupportOperator Support/support-ticketsactive human staff sessionOperator-shared support conversations, replies, and reopening.
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.
OperationsMarket PnL/market-pnltrades:read and redemptions:readResolved-market confirmed user cash flow and reference-only accumulated quoted fees.
OperationsCash Flow Triage/market-pnl-issuestrades:read, redemptions:read, and balance_operations:readRead-only source records, redacted wallet evidence, and resolution history behind PnL warnings; escalate to Polynion for reconciliation.
OperationsOpinion Settlement Reports/settlement-reportssettlements:readOperator-local monthly fees, captured principal closures, payout cash, net due, and CSV/PDF exports.
OperationsBalance Ops/balance-operationsbalance_operations:readOpinion wallet debits, credits, reversals, retries, balance-after evidence, and exports by default; use Polyflight → Wallet Operations for Polyflight.
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.
PolyflightWallet Operations/polyflight/balance-operationspolyflight:read and 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.
OperationsMarket Requests/market-requestshuman staff with markets:readUnreleased: review submitted private-market terms and approval/rejection history.
OperationsRequest Create Market/market-requests/createhuman staff with markets:read and markets:writeUnreleased: submit exact private-market terms and accept operator underwriting risk; does not publish.
SimulatorSimulator/simulatorsimulator:readStaging-only launch drill page for simulator users.
SimulatorSimulator Users/simulator/userssimulator:readStaging-only simulator user and balance management.
IntegrationsIntegration UAT/integrations/uatat least one relevant integration/operations scope; actions need their own grantsGuided integration evidence checklist.
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.

Availability: this table describes repository capabilities, not a deployment or acceptance record. Private Market Requests are marked Unreleased in the changelog; do not rely on them until Polynion confirms availability for your environment. Integration UAT appears with any of wallet_adapter:read, wallet_adapter:write, launch:write, webhooks:read, trades:read, or balance_operations:read; access to the page does not authorize every action.

Overview cards summarize users, generated fees (all time and last 24 hours), and visible open markets. They are not a wallet balance, operator earnings statement, or proof of settlement. For restricted staff, use the detailed pages for which access is granted rather than interpreting an unavailable metric as zero activity.

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 subsequent delivery attempts. Replay redelivers the same event identity and event time, but Opinion payloads are reconstructed from current order data on each send; JSON fields such as order status need not match an earlier attempt.
  • 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.
  • Support tickets create conversations with Polynion Support; they do not change wallet, trade, or settlement state.
  • Market Requests, when available, submit immutable terms for Polynion review. Submission is not market publication.

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
  • Operator pages do not mark cash outcomes completed/failed, send compensating money, waive unpaid payouts, or finalize/pay Opinion settlements. The Polynion Admin link in Cash Flow Triage requires separate authorized Admin access; dashboard staff access does not grant it.
Copyright © 2026