Players: manage the player lifecycle

What to watch for

• Account state, tier, verification and screening status sit together at the top of the record.
• The verification attempt has its own timeline, so a stalled check is visible rather than inferred.
• Every view of a player's document is itself an audited event with a named actor.

The player record opens on the facts a reviewer needs before doing anything else: whether the account is active, which compliance tier the player sits in, whether identity checks have cleared, what the screening result was, whether two factor login is on, and whether the email is confirmed. Those are separate states, and the platform shows them separately rather than collapsing them into one word.

Underneath, the record splits into identity, documents, the current review, the decisions taken and the raw data behind them. The verification attempt carries its own timeline from queued to pending to reviewed, with the time spent at each stage. The audit list at the bottom records who looked at what, so opening a player's identity document is an event with a name attached rather than an invisible action.

The still frame

The poster shows a player record: the player name with status chips for account, tier, KYC, AML, two factor and email across the top, a tabbed view underneath, a verification attempt timeline running from queued to reviewed, and an audit list of recent identity events.