AdminOrg-level settings — plan tier, billing, and org identifier. Start here before configuring team members or API keys.When: During initial setup or when updating billing/plan information.

Details

What this page is forOrg-level settings — plan tier, billing, and org identifier. Start here before configuring team members or API keys.

When to use itDuring initial setup or when updating billing/plan information.

Powered byNo specific bot dependency

Settings — Organization

Org identifier, plan tier, and billing contact. Changes require Admin role and are logged in the Audit Log.

Organization Team & Roles Wallets & Keys API & Integrations Notifications Display Audit Log

Organisation identity

Used in envelope headers and on-chain identifiers.

Org name Org ID Timezone

Plan & billing

Current plan tier and billing contact. To upgrade, contact your account manager.

Pro tier Renews 1 Jun 2026 · pUSD billing

Billing email

Locked rules

These rules are enforced at the platform level and cannot be changed here.

Settlement asset: pUSD only (no USDC.e, no fiat)
Exchange: CTFExchangeV2 (no V1 codepaths)
All orders must carry a valid builderCode
109 bot specs are frozen — no new bots may be introduced
Operator names, copy-trading sources, and insider feeds are forbidden inputs
Signing: EIP-712 v2

demo-wired ≠ production-live

Settings changes in this mock do not persist. In production, all org-level changes require Admin role and generate an entry in the Audit Log with reason code GOV_SETTINGS_CHANGED.

Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline