Skip to main content
Role-based access control (RBAC) in the StableFX Console governs what each user can see and do, with roles assigned at the account level across all users in an organization.

Account types

The console supports two account types that determine the trading perspective: Users with access to both types can switch between them using the account type dropdown in the sidebar navigation. The selection controls which data is displayed and which actions are available.

User roles

Each user is assigned one or more roles that control their permissions in the console:

Taker roles

Limited AR (Auto-Rate) roles can create trades and fund settlements only up to the pre-approved auto-rate limits configured for the account. Actions that exceed those limits require approval from an Admin.

Maker roles

Limited AR (Auto-Rate) roles can sign and fund trades only up to the pre-approved auto-rate limits configured for the account. Actions that exceed those limits require approval from an Admin.

Admin capabilities

Account administrators can:
  • Add and remove team members
  • Assign roles and permissions to users
  • Generate, rotate, and revoke API keys
  • Configure trading parameters (for example, risk buffer percentages)
The Admin role is typically assigned to the account owner during onboarding. Additional admins can be added through the team management interface.

Permission-gated features

Certain features in the console are only visible or accessible based on your role: If a feature is not available, you see a read-only view without action buttons. Contact your account administrator to request additional permissions.

API key permissions

API keys generated through the console inherit permissions based on their type:
Maker accounts cannot create quotes or trades via API, even with a Read & Write key. These operations are restricted to taker accounts.
For details on API key management, see API keys. To use these permissions in practice, see:

Onboarding requirements by role

Users with a Read Only role are exempt from individual KYC screening. All other roles require screening before access is granted.

Compliance controls

The console enforces several compliance controls:
  • IP-based geo-blocking: Access is restricted from sanctioned and high-risk jurisdictions.
  • Sanctions screening: All non-viewer users undergo automated sanctions screening during onboarding and on an ongoing basis.
  • Mainnet gating: Users cannot access mainnet if any sanctions screening alerts are unresolved.
  • Activity logging: All actions (trades, signatures, API key changes, role assignments) are logged with user ID and timestamp for audit purposes.

See also