Operator guideENplayerssanctionsrestricted-users

Players / Sanction List

Restricted-user maintenance and sanctions synchronization screen for manually managed and auto-generated sanctions matches.

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 / Sanction List is the restricted-user maintenance page. It combines search and validation filters, statistics, CSV export, manual create/update workflows, and a synchronization flow for sanctions data.

When to use it

Use this page when you need to:

  • check whether a person already exists in the restricted-user dataset
  • review manual versus auto-generated sanctions matches
  • add or update a restricted-user record
  • trigger a sanctions synchronization

How to read it

The page includes:

  • a filter block with name, country, date-of-birth, reason, validity, and source controls
  • top summary cards grouped by exclusion reason
  • a dense table of restricted users
  • dialogs for create, update, and sync confirmation

Important caveats

  • Status on this page is validity of the restricted-user record, not player account status.
  • Source is a separate column and filter that distinguishes manual and auto-generated entries. Status and Source should be read together, not as one combined field.
  • The top cards do not show global totals. They show counts by exclusion reason for currently valid records only.
  • Updating a player's identifying data can trigger sanctions checks elsewhere in backend logic, so this page is not the only place where sanctions outcomes matter.

Verification status

  • status: verified_backend
  • last verified: 2026-04-18
  • note: FE hooks, exclusion-reason lookups, create/update/sync flows, and the by-reason summary cards are traced through UserController and GetRestrictedUsersService.
Grid columns

Columns

field

Full Name

Human-readable restricted-user name.

Data Type
string
field

Country

Country code attached to the restricted-user record.

Data Type
string
field

Date of Birth

Birth date used for matching and review.

Data Type
date
field

Exclusion Reason

Reason category assigned to the record.

Data Type
string
field

Status

Validity badge for the restricted-user record. This is separate from the `Source` column.

Data Type
enum
field

Source

Separate badge showing whether the restricted-user record was auto-generated or created manually.

Data Type
enum
Filter dictionary

Filters

field

General Search

Searches across name fields.

Type
text
field

First Name

Restricts the list by first name.

Type
text
field

Last Name

Restricts the list by last name.

Type
text
field

Full Name

Restricts the list by combined name.

Type
text
field

Country Code

Restricts the list to one country code.

Type
text
field

Date of Birth

Exact date-of-birth filter for one restricted-user birth date.

Type
date
field

Date of Birth From

Lower bound for the date-of-birth range filter.

Type
date
field

Date of Birth To

Upper bound for the date-of-birth range filter.

Type
date
field

Exclusion Reason

Restricts the list to one reason category.

Type
select
field

Status

Filters by valid or invalid restricted-user records.

Type
select
field

Source

Filters by manual or auto-generated records.

Type
select
Metric dictionary

Metrics

metric

Exclusion Reason Count

Count shown in one top summary card for a specific exclusion reason. The FE renders one card per `stats.byReason` entry.

Data Type
integer
Verification State
verified_backend
metric

Exclusion Reason

Exclusion reason name used as the label of one top summary card.

Data Type
string
Verification State
verified_backend
Operational notes

Notes

item

The FE also loads exclusion reasons from `/api/admin/get-exclusion-reasons`.

item

`GetRestrictedUsersService` returns summary statistics with `total`, `valid`, `autoGenerated`, `manual`, and `byReason`, but the current FE top cards only render the `byReason` set.

item

Backend user-update flows can trigger sanctions checks outside this page.

Related references

Related pages

pageDashboard / Player Statistics

Top-player table for winners, losers, and depositors, with rank, player identity, level, and amount shown in a compact comparison view.

pagePlayers / Activity Log

Standalone player activity history page with filters for activity, device, date range, PID, country, tags, and comment-group context.

pagePlayers / API Requests

Inspection page for player-related API event logs, with payload search, system and time filters, row-level JSON export, and a three-mode request/response viewer.

pagePlayers / Banking

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

pagePlayers / Bonus Detail

Read-only detail page for one issued bonus, showing user, bonus, transaction, issuer, game, and lifecycle metadata.

pagePlayers / Bonuses

Cross-player issued-bonus inventory with server-side filters, preview popover, CSV export, and navigation into one issued-bonus detail page.