Players

The players area is the operator's window into every registered account — searching for someone, reading their full history, and stepping in when needed.

Finding a player

The list view supports searching by email or name, filtering by VIP level, and sorting (newest first by default), paged twenty at a time. Each row is a compact profile: balances split into real and bonus, lifetime deposits and wagering, profit and loss, VIP level, join and last-active dates, and status flags for verification, 2FA, and whether the account is blocked.

You can also kick off a manual balance transaction straight from a row — a deposit, withdrawal, adjustment, or bonus — which routes through an audited operation rather than touching the ledger directly.

The player profile

Opening a player gives a tabbed detail view that pulls their whole footprint into one place:

• Profile — edit identity and account fields (name, email, country, date of birth, affiliate tag) and VIP attributes (XP, level, tier, rakeback). This is also where you suspend or unblock an account, reset 2FA, or delete the player.
• Wallets — the player's per-currency wallet addresses.
• Bets — recent betting history.
• Transactions — the ledger.
• Sessions — active sessions, each revocable.
• Attribution — where the player came from: UTM source, medium, campaign, term and content, referrer, landing page, and IP.
• KYC — the verification workflow.
• Segments — which segments the player is in, with the ability to add or remove a manual one.

Interventions and who can do them

The split between reading and acting maps onto permissions. Viewing players needs players.view; editing, blocking, and managing sessions need players.edit. Balance corrections are separate and need balance.correction.manage, and the KYC actions need the players.documents.* permissions.

KYC

Identity verification runs as a small workflow on the KYC tab: a document can be requested, then approved or rejected. Approving a player is one of the events that re-runs their segment membership, since verification status is something segments can target. The player sees their status reflected in their own settings.

Manual segments vs dynamic ones

A player can be placed in a segment by hand from this screen, and that assignment is marked as manual. It coexists with the dynamic memberships the rules engine maintains — a manual assignment isn't swept away when dynamic segments recalculate. The mechanics of the rules engine are covered under Dynamic segments.