Page body
What this module covers
Players is the main operator module for finding a player, opening the player workspace, checking player-side activity, and following related workflows such as bonuses, sanctions checks, API logs, and player-specific reports.
For most backoffice teams this module answers four practical questions:
- how to find the correct player or lead quickly
- how to move from list view into a full player workspace
- where to inspect supporting context such as activity, bonuses, API requests, and sanctions data
- where player-level KPI and report tabs live once the profile is open
Surface map
Main list surfaces
- Player list
Default operational entrypoint at
/players. Used for search, filtering, CSV export, and opening the player workspace. - Leads
Reuses the shared player-table shell with
userType="lead"and lead-specific permission plus CSV import behavior.
Player workspace
- Player detail workspace
Main operator workbench at
/player/[playerId]with tabs, player-level actions, and modal-based workflows. - Player Overview Default visible profile tab with identity, compliance, limit, and affiliate fields.
- Player KPI Summary
High-density player summary backed by
/api/core/users/:userId/kpi. - Player Game Report Per-player game/provider breakdown.
- Player Session Report Per-session timeline and session aggregates with CSV export.
Relation and support pages
- Activity Log Standalone activity/history search surface for operators.
- API Requests Request/response inspection page for player-related API traffic.
- Player Bonuses Cross-player issued-bonus inventory with preview and detail navigation.
- Player Bonus Detail Read-only detail page for one user bonus.
- Sanction List Restricted-user maintenance and sanctions synchronization workflow.
How operators usually move through this module
- Start in the player list or leads list.
- Open the player workspace from the email or edit action.
- Use tabs and action buttons on the player workspace for direct operator actions.
- Jump to standalone relation pages when the task is history-heavy, bonus-heavy, sanctions-heavy, or API-trace-heavy.
Important caveats
- The current
Playersheader shows aCreate Playerbutton, but the page code does not route to a standalone create screen yet. - Player editing is therefore handled from the player workspace, tab content, and modal-based actions instead of a dedicated
/players/createflow. - Player-specific reports live under the player workspace tabs, not under
/players/*routes. Players / Bonusesis the cross-player issued-bonus inventory. The player-detailBonusestab is a different surface with its own local filters and actions.
Search hints
Search this module by:
- player list
- player profile
- player workspace
- leads import
- player bonuses
- sanctions list
- player api logs
- player activity log
- player kpi summary
Verification status
- status:
verified_fe_only - last verified:
2026-04-18 - note: module decomposition is confirmed from
nx-admin-fe-workspace; subpages carry their own backend verification depth.