Operators

An operator is a company that owns one or more brands. Its settings act as defaults for every brand beneath it, and each brand can override those defaults with its own configuration. Managing operators here keeps company-level details, integrations, and policies in one place so new brands start from a consistent baseline.

Terms used on this page

Know Your Customer (KYC) is the identity-verification process for a Player. Two-Factor Authentication (2FA) is a second authentication factor used during sign-in.

Term	Meaning
Know Your Customer (KYC)	Identity verification required by regulation before a player can withdraw.
Two-Factor Authentication (2FA)	A second login factor for backoffice users, on top of a password.

Accessing Operators

The Operators entry sits in the Settings section of the sidebar. Opening it shows the Operator Management page — the list of every operator and the entry point for editing one. Creating a new operator is reserved for super admins.

Operator list

The page shows a filter bar (search and status) above the operators table, with pagination beneath it. This is a plain, searchable list.

List columns

Column	Description
Operator	Operator name with its code shown beneath
Contact	Contact email, with phone shown beneath
Status	Active or Inactive
Created	Creation date
Actions	Edit

Filtering operators

Use the filters to find an operator quickly when the list grows.

• Search — match by name, code, company, or email
• Status — show only Active or only Inactive operators

Editing an operator

Click Edit on a row to open the operator's configuration, organized into grouped tabs. These settings are the defaults every brand under the operator inherits, so editing them updates the starting point for all of those brands.

General

Keep the operator's identity and contact details current, and confirm the currency its reports use.

Field	Description
Name	Display name (required)
Email	Primary contact email (optional)
Phone	Contact phone number (optional)
Reporting Currency	Currency all financial reports across this operator's brands are shown in. Set when the operator is created and cannot be changed here.
Code	Unique identifier (read-only)

Image Settings

Set the default image variant sizes so every brand under the operator starts from the same baseline; brands can override these with their own sizes.

Languages

Control which languages brands can offer players.

Setting	Description
Available Languages	Languages the platform supports
Default Language	Fallback language
Sort Order	Display order in selectors

You can add and remove languages, set the default, and reorder the list.

Countries

Control where the operator's brands accept players and which jurisdictions are blocked — a core part of staying within each market's regulations.

Setting	Description
Available Countries	Countries where the platform operates
Restricted Countries	Blocked jurisdictions
Sort Order	Display order in selectors

You can add and remove countries and reorder the list.

Integrations

Connect the external services brands rely on.

• Game Aggregators — the game-provider integrations whose titles brands can offer.
• Payment Gateways — the payment providers players use to deposit and withdraw.
• Banks — the banks available for manual bank-transfer payments.
• Anti-Fraud — the anti-fraud provider that screens player activity.
• Notifications — the default channels (for example email and SMS text messages) used to reach players; brands inherit these unless they set their own on the brand-level Notifications tab.
• AI Provider — the Artificial Intelligence (AI) provider behind AI-assisted backoffice features.
• Image Generation — the AI provider used to generate images.

KYC

Define the identity-verification reasons and the provider the operator uses. Identity verification is a regulatory requirement before a player can withdraw.

Social Networks

Set the social-network icons shown across the operator's brands. Upload a custom icon for any network, or clear it to fall back to the default.

Operations

Reasons and policies that govern manual money movements and wagering.

• Top-up Reasons — the reasons an operator can pick when manually adding funds to a player, each with a chosen effect on financial reports, so manual credits stay auditable.
• Confiscation Reasons — the reasons for confiscating funds, each with a chosen report effect.
• Deposit Wagering — the baseline deposit wagering policy that brands inherit.

Analytics

Choose how error monitoring loads on the player-facing website — load immediately, load after the page, load only when an error occurs, or disable it. Brands inherit this and can override it.

Passwords

Set the default password rules and hashing method for users under the operator. Brands can still override either setting.

2FA Settings

Available to super admins only. Turning on Enforce 2FA requires every backoffice user under this operator to enroll a Passkey or authenticator before they can continue. Enabling enforcement signs out affected users; existing methods are retained. Recovery codes alone do not satisfy enrollment. See Multi-factor authentication.

Creating an operator

Only super admins see the Create Operator button. Creating an operator needs just two values:

Field	Description
Name	Display name (required)
Default Currency	Required. Becomes the operator's reporting currency and is used for affiliate commissions and other currency conversions. It cannot be changed afterward, so choose carefully.

Everything else — contact details, integrations, languages, countries, and policies — is configured afterward on the operator's tabs.

Operator hierarchy

Operator
├── Brand 1
│   ├── Players
│   ├── Games
│   └── Settings
├── Brand 2
│   ├── Players
│   ├── Games
│   └── Settings
└── Defaults
    ├── Languages
    ├── Countries
    └── Providers

Each operator is independent. Players belong to a specific operator's brands, settings are operator-specific, and backoffice users can be scoped to a particular operator.

Best practices

• Keep the operator's name and contact details current.
• Choose the default currency carefully at creation — it becomes the reporting currency and cannot be changed later.
• Configure supported languages and countries before launching a brand.
• Review country restrictions against each market's regulations.
• Send a test notification after configuring a provider, before going live.
• Enforce 2FA for operators whose users need stronger account security.

Troubleshooting

Notifications not sending

1. Confirm the notification provider's credentials on the Notifications tab.
2. Check that the provider account is active with the provider.
3. Verify the from address or sender number.

AI features not working

1. Confirm the AI provider's credentials on the AI Provider tab.
2. Check that the account is within its usage limits with the provider.
3. Verify the selected model is available.

Reports show the wrong currency

1. Check the reporting currency on the General tab.
2. Remember it is fixed to the default currency chosen when the operator was created and cannot be changed afterward.

Related topics

• Brands
• Users & Roles
• API Keys