Admin panel
Admin — platform admin and client cabinet
The admin panel has two sides. Both use the same address and sign-in form; the account decides which side you get.
| Platform admin | Client (operator) | |
|---|---|---|
| Who | The platform owner and platform staff (owner, operator, viewer) | A company that integrates the platform: role client, and the team members it creates (client_user) |
| Created by | The owner, in Staff | Only the platform owner, by hand, in Clients |
| Sees | Every project, global settings, game catalogue, billing, staff, clients | Only its own projects (the partner ids the owner assigned) |
| Can change | Everything | Its own API key, callback URL, IP list, bet limits (inside platform bounds), players' RTP, free spins, target outcomes, cabinet and team |
The split is enforced on the server for every request, not only in the menu. A client that asks for another project's data, or for a platform-only action, receives 403 FORBIDDEN. Lists, reports, history and logs contain only the client's projects.
Platform admin: Clients#
Clients (owner only) is where clients are created and managed. Self-registration does not exist.
| Field | Notes |
|---|---|
| Username | Set at creation |
| Temporary password | At least 8 characters. The client must replace it at first sign-in; until then every other screen is locked |
| Projects | The partner ids the client may see and manage. A client with no projects sees nothing |
| Client permissions | game-history, api-logs, launch-game, freespins-view, freespins-grant, freespins-delete, configure-projects (bets and target outcomes), players-rtp, manage-credentials (API key, callback, IP list), manage-users (team members) |
| Company, e-mail, phone, website | The client's profile; the client can edit it later |
| Platform note | Visible to the platform only |
| Bet bounds | Optional per currency minimum and maximum stake per spin. The client's bet limits, global and per player, must stay inside |
| Enabled | Disabling a client also locks every team member of that client at once and ends their sessions |
Editing a client's projects or permissions ends its sessions and trims its team members to the new, smaller scope. A password entered while editing is a new temporary password: the client must change it at next sign-in. The Staff screen lists platform staff only; clients are never created or edited there.
Client: what the menu shows#
A client sees only the screens it has permission for.
| Screen | Needs | Notes |
|---|---|---|
| Dashboard, Analytics, Online | — | Reports and GGR of the client's projects only |
| Projects | — | Own projects. Tabs: Overview, Integration, Bet management. Other settings (RTP system, providers, technical, alerts, cabinet type) are platform-only and shown to the platform |
| Game History, API Logs | game-history, api-logs | Rounds and wallet callbacks of own projects |
| Free spins | freespins-* | Grant, view and cancel for own projects |
| Target outcomes | configure-projects | Own projects |
| RTP & players | players-rtp | Players' personal RTP and per-player bet limits. The project-wide RTP rule stays with the platform |
| IP Whitelist | manage-credentials | Own projects' networks only |
| Launch game | launch-game | Test launch for own projects |
| My cabinet | — | Profile, password, team, activity |
Not available to clients: Staff, Clients, Billing, provider and catalogue switches, release and system pages, the audit of other accounts, and revealing an existing API key.
Client: API key, callback and IP list#
Open Projects → project → Integration.
- The screen shows the partner id and the masked key with its fingerprint.
- Regenerate issues a new key. It is shown once, in the dialog — copy it then. The old key stops working immediately. You must type the project id to confirm.
- Revoke invalidates the key without issuing a new one. Casino requests fail until you regenerate.
- Callback URL — enter an
https://address on a public host, Save, then Test connection. - IP Whitelist — add or delete the networks that may call the API for your projects (Authentication). Removing every address of your own server blocks your integration.
Key, callback and IP changes are written to the audit log with your account.
Client: My cabinet#
- Company profile — name, contact e-mail, phone, website. The platform's bet bounds for your account are shown read-only.
- Password — change your own password. Other sessions of your account end.
- Team (needs
manage-users) — create team members. A member gets a login and temporary password, a subset of your projects and a subset of your permissions. You cannot give a member more than you have, and a member can never manage the team (manage-usersis never delegated). You can narrow a member, disable it or reset its password. If the platform later narrows your own scope, your members lose it too. - Activity — the log of actions of your account and your team.
Team members see the same menu limited to their projects and permissions, cannot edit the company profile and cannot see other members.
Related#
- Getting started — sign-in and screen map.
- Access, staff and history — platform staff and the audit trail.
- Authentication — API key and IP allowlist from the integration side.