.png?fit=max&auto=format&n=ML35RDblT1Ol-zJb&q=85&s=062e79ad9c4540929eec204aff020178)
.png?fit=max&auto=format&n=ML35RDblT1Ol-zJb&q=85&s=f6328956931c9664a2a070c2edb6e9b3)
OpenXSwitch provides Team Management features that enable businesses to securely collaborate across operational, engineering, compliance, and finance teams through role-based access controls and workspace-level permissions. This allows organizations to manage access to wallets, APIs, webhooks, transactions, compliance tooling, and operational infrastructure while maintaining security and auditability.Documentation Index
Fetch the complete documentation index at: https://docs.openxswitch.com/llms.txt
Use this file to discover all available pages before exploring further.
Key Features
- Create & Manage Teams - Organize users into teams for structured operational collaboration.
- Role-Based Access Control (RBAC) - Assign predefined roles with scoped permissions.
- Secure API & Webhook Management - Restrict access to sensitive infrastructure configurations.
- Multi-User Workspace Access - Allow multiple users to securely operate within a single business workspace.
- Audit Logging - Track operational actions, permission changes, and team activities.
- Granular Security Controls - Limit access to wallets, transactions, and administrative actions.
How to Add a Team Member
To enable collaboration within your organization, administrators can invite users into a workspace through the OpenXSwitch Console.Steps to Invite a Team Member
- Navigate to Accounts → Team within the OpenXSwitch Console.
- Click New Team Member.
- Enter:
- Team name
- Member email address
- Select a role:
- Administrator
- Operator
- Developer
- Viewer
- Click Confirm & Submit.
Role & Access Management
OpenXSwitch uses Role-Based Access Control (RBAC) to ensure users only have access to the resources and actions required for their responsibilities.| Role | Permissions |
|---|---|
| Administrator | Full workspace access including team management, API management, wallet operations, billing, compliance tooling, and member invitations/removals. |
| Operator | Manage wallets, transactions, treasury operations, automation rules, and operational workflows. |
| Developer | Access APIs, webhooks, transaction monitoring, and developer tooling. Cannot manage team or administrative settings. |
| Viewer | Read-only access to dashboards, transaction history, analytics, and operational reporting. Cannot perform state-changing actions. |
Security & Compliance
| Feature | Description |
|---|---|
| Granular Access Control | Restrict access to sensitive operational infrastructure and financial actions. |
| Audit Logs | Monitor team activity, permission changes, authentication events, and operational actions. |
| Secure API Key Management | Administrators can create, rotate, revoke, and manage API credentials securely. |
| Workspace-Level Isolation | Team permissions and operational access are isolated per business workspace. |
| Operational Security | Designed to support enterprise operational controls and internal governance requirements. |
Best Practices
- Assign users the minimum required permissions.
- Restrict administrative privileges to trusted personnel only.
- Rotate API credentials periodically.
- Monitor audit logs for sensitive operational changes.