Dashboard and your operations
Run your business, manage staff and configuration, and reconcile activity.
The Partner Dashboard is your team's operational workspace. It complements the API your backend uses and the interface your users see. Staff sign in using email OTP after their email is granted access to your organization; an end-user account or API key does not grant dashboard access.
What your team can see
The portal brings together trading volume, fees, payout history and users. User detail views connect your user’s display identity with managed wallet, trades, positions and P&L. Historical trends help your team understand activity over time. Optional traffic analytics cover configured website traffic separately from trading activity.
Treat reporting as reconciled data rather than a promise of instantaneous settlement. A collected program fee is not all your revenue: distinguish your treasury share, user referral allocations, pending transfers and paid amounts. One combined referral payout may cover several days; count the transfer once.
Staff roles
| Capability | Owner | Operator | Analyst |
|---|---|---|---|
| View your organization’s reports and user detail | Yes | Yes | Yes |
| Pause/resume new orders | Yes | Yes | No |
| Manage permitted referral-program settings | Yes | Yes | No |
| Manage realtime browser origins | Yes | No | No |
| Change payout wallet | Yes | No | No |
| Add operators and analysts | Yes | No | No |
CRISP assigns the initial owner. Your organization has one active owner, and an active staff email can access only one organization at a time. Access is checked on each protected request; revocation blocks subsequent access even if a browser still holds a session. Coordinate ownership transfers with CRISP.
Pause new trading
Owners and operators can pause new orders across your organization and resume them when appropriate. Cancellation and position redemption remain available during this new-order pause. This control does not cancel resting orders or reverse fills. Distinguish a pause initiated by your team from a venue restriction or an account-specific issue when communicating with users.
Manage your program
Review fees and revenue and referral behavior before changing settings. Program and payout-destination changes apply through new versions; they do not rewrite previously accepted orders or settled history. Treasury payout cadence and thresholds are separate operational settings to coordinate with CRISP.
Keep users up to date
Use account sync to refresh balances, orders and rewards in your application. Backend consumers can use account-update cursor reads. Events are notifications to refresh or reconcile authoritative resources, not proof that money has arrived. Webhooks are not part of the standard offering; discuss specific server-to-server automation needs with CRISP for separate assessment.
Your owner manages exact browser origins in Trading → Realtime browser origins. Up to 20 exact HTTPS origins are supported, with HTTP allowed for localhost development. Removing an origin blocks new connections and reconnects; it does not disconnect already established sessions. See account updates for account sync, backend cursor reads and recovery behavior.
Escalation and incident handling
Agree a support contact, escalation channel and incident communication process before launch. Provide safe request/operation IDs, timestamps and the affected action when reporting an issue. Do not send API secrets or signing material.
For an uncertain trade or transfer, preserve its original intent and show pending confirmation until reconciled. A manual-review payout is not paid. Rate limits, service commitments, maintenance notices and replay procedures belong in the agreed operating arrangements, not assumptions based on a successful test request.
Next: onboarding and launch planning or the technical launch checklist.