Skip to main content

Operator Roles

Operator roles decide which pages each member of your team can open in Operator Controls and what they can do there. They're managed under Operator Controls → Exchange → Access Control, which has three pages: Operator Roles, Role Management and System Permissions.

Dashboard roles vs operator roles

These are separate. Dashboard member roles (owner, admin, tech, billing, business) control what someone can do in the Cloud Dashboard and whether they can open Operator Controls at all. See Account, Security & Team Members. Operator roles, described on this page, control what an exchange operator account can see and do inside Operator Controls.

Built-in roles​

Your exchange comes with built-in roles. Operator Controls describes them as follows:

RoleWhat it's for
AdminFull, unrestricted control of the exchange: settings, assets and markets, funds, users, and the operators and roles themselves. The admin role's permissions can't be edited.
SupervisorRuns day-to-day operations: manages user accounts, banking details and sessions, and reviews orders, trades, deposits and withdrawals.
KYCHandles identity verification: reviews users, verifies or revokes bank accounts, confirms emails and upgrades verification levels.
CommunicatorOwns content and communications: edits exchange branding, strings and pages and uploads assets. No access to users or funds.
SupportFront-line support: looks up users and reads their orders, trades and transactions, and leaves notes. Can't move funds or change exchange settings.

Your exchange may have other built-in roles, such as Announcer or Audit. Role Management shows every role on your exchange and exactly which permissions it holds, so check there before you assign one.

Operator Roles: assign roles to operators​

The Operator Roles page shows your current role and what it can access, the role types on your exchange, and Active Operators: the users who hold an operator role.

To add an operator:

  1. The person needs a user account on your exchange first.
  2. Click Add New Operator.
  3. Under Email Address, search for the user by email.
  4. Under Select Role, choose a role. If there are no roles yet, create one first in Role Management.
  5. Click Add Operator.

If your plan doesn't include team management, the dialog shows an upgrade prompt instead. Contact the HollaEx team to find out what your plan includes.

To change an operator's role, use Edit User Role. To remove someone's operator access, use Revoke Role. Use Search user to find an operator by email.

Role Management: create and edit roles​

Role Management lists every role as a card with its permission count.

  • EDIT PERMISSION opens a role's permissions.
  • Delete removes a role. The Admin role can't be modified or deleted.
  • Create New Role adds a role.

You need two-factor authentication turned on for your operator account to create or edit roles.

To create a role:

  1. Click Create New Role.
  2. Choose a starting point: Blank role, or an existing role to copy its access as a starting point.
  3. Enter the role name, a Description and a Role Color.
  4. Select the permissions. Critical permissions are marked with a warning. Permissions are grouped in tabs:
    • Access (or API Routes): the actions the role can take, such as reading user balances, verifying bank accounts or creating deals.
    • Restriction: optional limits for the role, such as Max visible user verification level, Max approvable transaction (USDT) and Daily mint/burn limit (USDT, per operator). Leave a field empty for no limit. Limits are valued in USDT and enforced by the server.
    • Kit Configuration: which exchange settings the role can change, such as visuals or fees.
    • Kit Secrets: access to sensitive settings, such as security settings and IP allowlists.
  5. Review the role details and confirm.

Example custom roles​

  • P2P disputes: as P2P trading grows, a role with only the P2P permissions can resolve disputes. See P2P.
  • Announcements: a role limited to announcement permissions lets a marketing team member post announcements without access to users or funds.
  • Audit: a role with read-only (GET) permissions can view the data and events needed for compliance without changing anything.

System Permissions: see every permission​

System Permissions lists every permission the system can grant, what it does, and which roles hold it, in three tabs: API Routes, Kit Configuration and Kit Secrets. Search, or filter by role or category, to answer questions like "which roles can approve withdrawals?".