WORKSPACE & SECURITY

Connect The Workspace Without Confusing Access With Authority

Manage settings, broker connections, preferences, and user access while keeping one rule clear: connected or configured does not mean authorized to trade.

PAPER MODE · LIVE OFFREAL CAPITAL OFFAI execution authority · NoneAI risk authority · None
TradeProcess AI illustrative workspace settings.
Simulated product view · Workspace Settings

WHY THIS MATTERS

A connected broker or configured workspace still does not mean live execution is enabled. Customer live broker execution remains off.

THE PROBLEM

Connected Does Not Mean Authorized

Settings can blur three different questions: what is configured, who can access it, and what the system is actually allowed to do. That distinction matters most around broker connections and financial permissions.

WHAT CHANGES

Separate Configuration, Access, And Trading Permission

Give users a clear place to manage configuration and connection state while the server continues to own authorization, tenant isolation, and trading-mode boundaries.

THE GOAL

Let users configure a workspace, preferences, access, and broker-connection metadata while keeping identity, tenant isolation, secrets, and trading authority server-owned and clearly separated.

THE INPUTS

Know What Is Configured, Who Can Access It, And What It Can Actually Do

Keep workspace settings, user roles, connection status, and trading permission visible as separate facts instead of collapsing them into one “connected” status.

INPUT / EVIDENCE

Authenticated workspace identity

The verified user and workspace/tenant context determine which customer data and settings may be accessed.

INPUT / EVIDENCE

User preferences and configuration

Workspace preferences can change the customer experience without silently changing safety-critical authorization.

INPUT / EVIDENCE

Broker connection metadata

Connection state and permission scope can be inspected without exposing secret credentials or implying live order authority.

INPUT / EVIDENCE

Role and access state

User/role permissions define who can view or change workspace resources while tenant boundaries remain enforced server-side.

WHAT YOU GAIN

Keep Configuration And Authority From Blurring Together

Give users a clear place to manage configuration and connection state while the server continues to own authorization, tenant isolation, and trading-mode boundaries.

  • See workspace and broker configuration without exposing secrets in the browser.
  • Distinguish connection state from permission to submit live orders.
  • Keep account and role access separate from strategy or risk authority.
  • Change preferences without widening deterministic trading boundaries.

HOW IT WORKS

Configure The Workspace. Keep Trading Permission Separate

Set workspace preferences, check connection status, manage user access, and keep trading permission separate from those settings.

  1. 01
    Verify identity and workspace

    Authenticate the user and resolve the authorized workspace before customer data or configuration is shown.

  2. 02
    Configure preferences

    Allow users to adjust permitted workspace settings while keeping safety-critical policy and secrets outside the browser.

  3. 03
    Inspect connections and permission scope

    Show whether a broker/service connection exists and what scope is configured without treating “connected” as equivalent to “authorized for live trading.”

  4. 04
    Enforce server-owned boundaries

    Tenant isolation, role authorization, deterministic risk, and trading-mode controls remain authoritative regardless of what the settings UI displays.

FEATURES IN DEPTH

Settings Should Make Permissions Clear

Workspace and broker-connection views should show what is configured without exposing credentials or implying authority the user does not have.

TradeProcess AI illustrative workspace settings.
PAPER MODE · LIVE OFF
PRODUCT VIEWWorkspace Settings

SUBFEATURE 01

Workspace Settings

Manage workspace preferences without letting a settings change widen server-owned trading authority. Customer configuration stays separate from the controls that decide whether exposure is permitted.

WHAT IT DOES

Give customers a clear place to manage permitted workspace preferences without mixing configuration with trading authority.

WHAT YOU SEE
  • Workspace-level preferences
  • Current effective configuration where exposed
  • Clear PAPER/live-off operating state
WHY IT MATTERS

Users can personalize the workflow while the server still owns identity, authorization, risk ceilings, and live-trading boundaries.

TradeProcess AI illustrative broker connections screen.
PAPER MODE · LIVE OFF
PRODUCT VIEWBroker Connections

SUBFEATURE 02

Broker Connections

Inspect connection state and permission scope while customer live broker execution remains explicitly off. Connection details can be visible without exposing secret credentials or implying live submit/cancel authority.

WHAT IT DOES

Expose connection and permission-scope state without exposing secrets or implying that a connected service may place live orders.

WHAT YOU SEE
  • Connection identity/status
  • Permission scope or environment context
  • Explicit distinction between connection state and live authority
WHY IT MATTERS

Financial integrations are safer when “connected,” “can read,” and “can trade” are treated as different states instead of one ambiguous toggle.

Boundary: Customer live broker execution remains off.

PRACTICAL USE CASES

The Moments When “Connected” Can Be Misread

The distinction matters when a broker is connected, a team member has workspace access, or a setting changes without changing trading permission.

SCENARIO 01

Connect a broker account for inspection without granting live execution

Connection metadata can be configured and verified while submit/cancel/replace authority remains disabled until a separately approved live-authority process exists.

SCENARIO 02

Add a team member without widening trading authority

A user can receive an appropriate workspace role while the platform continues to enforce tenant isolation and keeps strategy/risk/live-execution authority separate.

DEEPER PLATFORM COVERAGE

Manage The Workspace Without Expanding Trading Authority

Workspace configuration, preferences, team access, and secure-access views keep convenience separate from permission.

  • Workspace Configuration
  • Preferences
  • Team
  • Secure Access
  • User & Role Access

HOW IT CONNECTS

Security Supports Every Workspace, Even When You Do Not See It

Research, risk, PAPER Trading, and operations all depend on secure workspace separation, clear user roles, and protected connections—even when those controls stay in the background.

Governance

Defines role, tenant, entitlement, and audit semantics that keep administrative capability separate from trading authority.

Deterministic Risk

User preferences can request a risk configuration, but effective safety limits remain subject to server-owned ceilings and restrictions.

PAPER Trading

Broker or account configuration may provide context, but customer live execution remains off until separately authorized.

LIMITATIONS & BOUNDARIES

A Connected Account Still Does Not Mean Live Trading

A broker connection and workspace access can both be valid while live broker execution remains completely unavailable.

  • A configured broker connection does not imply permission to submit, cancel, or replace live orders.
  • Secrets should remain server-side and should not be exposed through browser-visible configuration surfaces.
  • A role, preference, or commercial entitlement cannot override tenant isolation or deterministic safety controls.
  • Requested user configuration may be more permissive than the effective configuration when platform safety rules are stricter.

SAFETY BOUNDARY

Configuration Can Change Preferences. Trading Authority Stays Server-Owned

AI execution authority
None
AI risk authority
None
Deterministic risk controls
Authoritative
Customer live broker execution
Off
Manual reduce / close during halt
Preserved

CAPABILITY QUESTIONS

Questions About Access, Connections, And Workspace Control

These answers clarify what users can configure, what stays server-owned, and why broker connection state is not the same thing as execution authority.

Does connecting an account turn on live trading?

No. Connection state and live-execution authority are separate. Customer live broker execution remains off until a distinct live-authority process is explicitly approved.

Can workspace settings weaken risk controls?

No. User-configurable values are bounded by server-owned policy and safety ceilings. The effective configuration can be more restrictive than the requested one.

Where are broker secrets handled?

The design keeps sensitive credentials out of browser-visible configuration. Connection and permission metadata can be shown without exposing the secret itself.

Does this capability change the PAPER / live-off boundary?

No. Customer execution remains PAPER / simulation and live broker execution is off. AI remains advisory and deterministic server-owned safety controls remain authoritative.

GUIDED TRADING INTELLIGENCE

Configure The Workspace. Keep Authority Explicit

Give users a clear workspace without allowing settings, roles, or connections to blur the line between access and trading permission.

Create your workspaceExplore other features
PAPER MODE · LIVE OFF · Customer live broker execution is off.