Operator guideENplayersdetailtabsactions

Players / Detail Workspace

Main player workbench at `/player/[playerId]` with tabbed sections, player-level actions, and modal-based operator workflows.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this page shows

Players / Detail Workspace is the main operator screen for one player. It combines identity and wallet context, operational tabs, report tabs, and a high-action header with player-specific workflows.

This page is the shell that owns the player workspace. Most player-facing CRUD and inspection surfaces are mounted inside this route rather than living on separate create/edit pages.

When to use it

Use this page when you need to:

  • inspect a single player in depth
  • change player-related state through modal actions
  • move between operational tabs such as Wallet, Banking, KYC, Fraud, or Activity Log
  • open player-scoped reports such as KPI Summary, Game Report, and Session Report

How to read it

The page has two important layers:

  1. Action bar at the top with mutation workflows such as comments, inbox, bonuses, wallet actions, tags, loyalty points, and audit history.
  2. Tabbed workspace where each tab focuses on one domain of player data.

The title combines the player's name, if present, with the internal userId.

The shell keeps two tab states:

  • currentTab for the currently visible tab
  • selectedTabs for tabs that were already opened once and stay mounted for the session

This means some heavy tabs are lazy-mounted on first access and then stay available without a full remount during later tab switches.

Main tabs

  • Overview
  • Wallet
  • Gaming
  • Banking
  • KYC status
  • Game report
  • NGR Timeline
  • Bonuses
  • Available Coupons
  • Available Bonuses
  • KPI summary
  • Fraud Detection
  • Comments
  • Inbox
  • Activity Log
  • API
  • Calendar
  • Referral Stats
  • Onboarding
  • Favorite Bonuses
  • Chat Messages
  • Session Report
  • Road Map

High-value actions

  • Add Comments
  • Send To Inbox
  • Add Coupon
  • Add Bonus Manually
  • Add Rakeback Manually
  • Manage wallet
  • Add Adjustment
  • Tags
  • Add Loyalty Points
  • Audit History

Known caveats

  • This workspace acts as the real edit surface for players. There is no separately verified /players/create or /players/edit route.
  • Some tabs are lazily mounted. Operators may see initial loading when opening a tab for the first time in a session.
  • Report-like tabs such as KPI summary, Game report, and Session Report are documented separately because they are data-heavy surfaces.
  • The current tab is mirrored in the URL query string as ?tab=<label>, which means copied URLs can deep-link into a specific tab.
  • The tab label Comments is not the same thing as the standalone /players/activity-log page. Inside the workspace it mounts PlayerActivities in COMMENT mode and the tab label also carries the current comment count.
  • The tab label Activity Log uses the same base component family as Comments, but it mounts the broader activity-history mode for one player instead of forcing COMMENT activity only.
  • Several action-bar buttons do not navigate away. They open always-mounted modal components that depend on the currently loaded player context and wallet state.

Verification status

  • status: verified_backend
  • last verified: 2026-04-18
  • note: the shell route, tab orchestration, comment-count label, and mounted modal stack are traced through usePlayer, useGetUserActivities, and the player page component; child tabs remain documented in their own packs.
Operational notes

Notes

item

The shell mirrors tab state into `?tab=<label>` and keeps previously opened heavy tabs mounted through `selectedTabs`.

item

`Comments` inside this route is not the standalone activity-log page. The shell uses `useGetUserActivities({ activityCode: 'COMMENT', ... })` to append a count to the tab label and mounts `PlayerActivities` in comment-only mode.

item

The same shell passes `depositWager` and `totalWagerSpend` from `usePlayer` into the banking tab, so some child tabs depend on shell-provided data rather than fetching those values independently.

Related references

Related pages

pagePlayers / Banking

Banking tab inside the player workspace with transaction filters, a paginated banking grid, analytics cards, CSV export, and automatic-withdrawal availability.

pagePlayers / Fraud Detection

Fraud-detection tab inside the player workspace with fraud risk assessment, related fraud reports, IP analysis, and identity-graph filtering.

pagePlayers / Game Report

Per-player game or provider report inside the player workspace, filtered by date option and grouped either by game or by provider.

pagePlayers / Inbox

Inbox tab inside the player workspace for reviewing sent notifications, filtering by read state or notification type, and resending or deleting messages.

pagePlayers / KPI Summary

Grouped player-level KPI snapshot inside the player workspace, covering player info, deposits, withdrawals, casino totals, bonus cost, and predictive metrics.

pagePlayers / KYC Status

KYC tab inside the player workspace for browsing user documents, checking third-party verification state, and approving, rejecting, or re-requesting documents.