Users

The Users page shows Mini App users created through launch requests for the authenticated operator.

Dashboard path

Operator Dashboard → Operations → Users

Required scope: users:read

What operators can do

• search by external user ID or display name
• filter by active, suspended, or disabled status
• confirm the linked Polynion user ID when one exists
• inspect last seen and creation timestamps
• page through 25 records at a time, newest-created first

Search and status changes apply immediately and reset pagination. The URL retains search, status, and page; Reset clears them. The table is read-only: it has no user-detail drill-down, export, balance editor, or suspend/disable action.

Source API

The page reads GET /api/operator/users.

The API supports the following query fields; only search, status, and pagination are exposed as controls on this dashboard page:

• status: active, suspended, or disabled
• search: matches external_user_id or display name
• external_user_id: exact operator user identifier
• created_from, created_to: UTC ISO windows
• sort: created_at_desc, created_at_asc, or external_user_id_asc

Table fields

• external user ID
• display name
• status
• Polynion user ID
• last seen time
• created time

Operational notes

external_user_id is the operator-owned stable user identifier. Use it in support, webhook, wallet adapter, and simulator investigations.

For an investigation, copy the external user ID into Trades, Market PnL, or Balance Ops, using each page's own filters and required scopes. These are separate navigation steps, not row actions on Users. Do not use a display name as an exact identity match or treat a missing linked Polynion ID as proof that money moved.

Escalate through Operator Support with the environment, external user ID, relevant IDs, and a UTC timestamp window. Never include launch tokens or credentials.

Disabling or suspending a user is not currently exposed from this page. User state changes must go through the owning control-plane flow.