Admin panel

Admin panel

The admin panel is the web console for your back-office staff. Everything you can do in it is also available over the API where the API reference lists a method; the panel's own endpoints are not a public API. This page lists the tasks, not individual screens, because the panel layout changes.

Open the panel at https://notellgaming.com/admin/ and sign in with your username and password. A session lasts 2 hours. Repeated failed sign-ins are throttled (AUTH_THROTTLED): wait a minute and retry.

There are two sides, chosen by the account:

	Platform side	Client side
Who	The platform owner and platform staff (`owner`, `operator`, `viewer`).	A company that integrates the platform (`client`) and the team members it creates (`client_user`).
Created by	The owner, in Staff.	Only the platform owner, in Clients. There is no self-registration.
Sees	Every project.	Only the projects assigned to it. Every request is checked on the server; another project's data is answered with `403 FORBIDDEN`.

What an account can do is set by permissions:

Permission	Allows
`game-history`	Round history.
`api-logs`	Wallet callback attempts.
`launch-game`	Test launch of a game.
`freespins-view`, `freespins-grant`, `freespins-delete`	View, grant and cancel free spins.
`configure-projects`	Change settings of the account's own projects (callback URL, providers, bet limits) and manage target outcomes.
`players-rtp`	Change a player's RTP and bet limits (client side).
`manage-credentials`	API key, callback URL, IP list and frame origins (client side).
`manage-users`	Create team members (client side).

The platform owner can do everything. A new viewer gets game-history and api-logs; a new operator gets all platform permissions except configure-projects. Give each person the least access they need.

Projects, keys and callback#

Open Projects, choose the project, then Integration. Who may change what: the owner, and staff or clients with configure-projects or manage-credentials for their own projects. Others see read-only forms.

API key. Shown masked with a fingerprint. The owner can reveal it. Regenerate issues a new key, shown once; the old key stops working at once. Revoke (client side) invalidates the key without a new one. Copy a new key immediately. See Authentication.
Callback URL. The base address of your wallet: https://, port 443, public host, no trailing slash. Use Test connection: it sends one session_info request and shows the HTTP status, latency and your answer. See Wallet callbacks.
IP list. The networks (CIDR, IPv4 or IPv6) that may call /gameActions.do and /playerRtp.do for the project. Removing every address of your own server blocks your integration. A request from another address gets IP_NOT_ALLOWED. See Authentication.
Frame origins. The sites that may embed the game in an iframe: up to 16 https origins, without wildcards, paths or credentials (for example https://casino.example). A site that is not on the list gets a blocked frame. Saving applies within about 15 seconds. See Embedding.

Other project settings:

Enabled switches the project on or off.
Default currency (any of the 157 supported currencies) and default language (ru, en or uk, used when a launch has no lang; see Languages).
Providers: per Endorphina, Pragmatic Play and Nolimit City, switches for the game, bonus buy, ante bet and gamble, where the provider supports them.
Bet management: the project bet-limit table (Bet limits). Both a minimum and a maximum are required for each currency entry.
Pragmatic Play label: which round data (round number, clock, session time, net position) the Pragmatic Play games show next to the logo.

Settings carry a revision: if a colleague saved first, your save is refused with PROJECT_SETTINGS_CONFLICT. Reload and repeat the change. Changes of limits, RTP and provider switches apply from the next round; rounds in progress finish as they started.

RTP and players#

Open RTP & players.

Project RTP (60–100 %, default 90 %), the Personal RTP switch and the adaptive rule are edited by the platform owner; others read them. Changes are saved automatically. See RTP management.
Players. Find a player by id (or by the nickname of a player of the platform's own site), see their level, mode and journal, and set a manual level (60–100 %), return them to auto, or set a personal bet limit. Platform owners and client users with players-rtp can change a player; a client's player limits must stay inside the bounds the owner configured for it. A manual level has an effect only while Personal RTP is on.
Per-game bet limits are set here too (Bet limits).

The same player actions are available over the API (/playerRtp.do).

Free spins, target outcomes and test launch#

Free spins screen: grant, view and cancel grants; the bet picker lists the game's valid bets, including extended bets. Permissions freespins-*. See Free spins.
Target outcomes screen: schedule and cancel entries (permission configure-projects). A site nickname can be entered instead of a player id. See Target outcomes.
Launch game: opens a game for a test player in any supported currency and language (permission launch-game).

Reports#

Dashboard, Analytics and Online: stakes, payouts, GGR, RTP, spins and players per project, provider, game and currency, and the players online now.
Game History (game-history): the round log with filters and the wallet operations of each round.
API Logs (api-logs): every wallet callback attempt with time, method, status, latency and error code; secrets are masked. Use it first when a launch or a bet fails.

The same data is available over the API as report_rounds, report_ggr and report_reconciliation.

Staff and roles#

Platform owner only. In Staff create and edit platform accounts: username, display name, role (operator, viewer or owner), password (at least 8 characters), enabled flag, permissions and the projects the account may see. A disabled account cannot sign in. Clients are not staff; they are created in Clients.

The panel keeps no separate audit screen. Sensitive actions (saving project settings, revealing or regenerating a key, changing the callback URL or frame origins, granting or cancelling free spins, scheduling target outcomes) are written to the platform's audit log with the acting account; contact the platform owner for an extract. Player RTP changes are in the player's journal.

Client cabinet#

Platform owner, in Clients: create a client with a temporary password (at least 8 characters; the client must replace it at first sign-in), the projects it may see, its permissions, optional per-currency bet bounds, and a profile. Disabling a client locks its whole team and ends their sessions. Changing a client's projects or permissions ends its sessions and narrows its team.

A client sees only the screens its permissions allow, for its own projects: Dashboard, Analytics, Game History, API Logs, Free spins, Target outcomes, RTP & players (player level and limits only), Projects (overview, integration, bet management), IP list and My cabinet. Platform-only settings (project RTP rule, providers, catalog switches, billing, staff, clients) and revealing an existing API key are not available to clients.

In My cabinet a client edits its company profile and password, and with manage-users creates team members: a member gets a subset of the client's own projects and permissions, never manage-users. If the platform narrows the client's scope, its members lose it too.

Sign in and roles#