Operator guideEN

Players / Sanction List

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

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page shows

Players / Sanction List is the maintenance page for people who should be treated as restricted users. It combines a searchable table, reason-based summary cards, manual create/update dialogs, CSV export, and a sync action for auto-generated sanctions entries.

When to use it

Use this page when you need to:

  • check whether a person already exists in the restricted-user dataset
  • review valid and invalid restricted-user records
  • separate manual records from auto-generated sanctions records
  • add a manual restricted-user record
  • invalidate or annotate an existing restricted-user record
  • trigger a sanctions-source synchronization
  • export the currently applied filtered result set

How to read the top cards

The top cards show counts by exclusion reason. They count valid restricted-user records grouped by reason.

These cards are not the same as the table result count. Table filters can narrow the grid, but the reason cards describe the broader valid restricted-user population returned by the page statistics.

How to read the table

The table shows restricted-user rows with name, country, birth date, exclusion reason, validity, source, comments, exclusion end date, timestamps, creator display, and an Edit action.

Status means whether the restricted-user record is currently valid or invalid. It is not the player's account status.

Source means how the restricted-user row was created:

  • Auto means the row came from the sanctions synchronization flow.
  • Manual means an operator created the row with Add User.

Compact View hides secondary columns such as Source, Comment, Exclusion End Date, Created At, Updated At, and Created By. It changes only the display density, not the dataset.

Filters

The filter block can search all name fields or narrow by first name, last name, full name, country code, date of birth, exclusion reason, validity, and source.

Date fields accept YYYY-MM-DD values. If exact Date of Birth is filled, it takes priority over the Birth Date From / Birth Date To range.

Apply Filters sends the visible filter state to the server-backed list. Reset clears the visible filters and reloads from the first page.

Add User

Add User creates a manual restricted-user record. Full Name and Exclusion Reason are required. First Name, Last Name, Country Code, Date of Birth, Comment, and Exclusion End Date are optional.

If First Name or Last Name is missing, the system can derive them from Full Name. Empty Exclusion End Date means the exclusion is permanent. A successful create adds a valid manual record and refreshes the table.

Edit

Edit is intentionally limited. It can change Status, Comment, and Exclusion End Date for the selected row.

It does not edit name, country, date of birth, exclusion reason, or source. Auto-generated rows can only be marked invalid from this flow; other edits to auto-generated rows are blocked.

Sync List

Sync List opens a confirmation dialog and then asks the system to refresh auto-generated sanctions rows from the configured sanctions source.

The sync can add new auto-generated rows, reactivate matching invalid rows, and update last-checked timestamps. In the current portal-triggered flow, the sync is sent with force update enabled, so operators should not assume the action will invalidate outdated auto-generated rows.

Manual rows are separate from synced rows. Sync does not turn manual rows into auto-generated rows.

Export

Export downloads a CSV using the currently applied filters. Unsaved filter input text is not included until Apply Filters is clicked.

The current export request starts from page one and requests up to 10000 rows. Export is disabled while the table is loading or when the current filtered result count is zero.

Important caveats

  • Status is restricted-user validity, not player account status.
  • Source and Status should be read together. A row can be auto-generated and valid, auto-generated and invalid, manual and valid, or manual and invalid.
  • The top cards are valid-record reason counts; they are not filtered table totals.
  • Created By can display System when the table payload does not expose creator details in the shape the UI expects.
  • Updating a player's identifying data can trigger sanctions checks elsewhere, so this page is not the only place where sanctions outcomes matter.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations9 topicsOpen details

Restricted-user filter query

The table reload is server-backed; filters are not just narrowing the currently visible browser page.

Inputs
General Search, First Name, Last Name, Full Name, Country Code, Date of Birth, Birth Date From, Birth Date To, Exclusion Reason, Status, Source
Transform
Applies text-name filters as lower-cased contains matches, exact country-code matching, exact or range date-of-birth filtering, exact exclusion reason matching, and exact boolean matching for Status and Source.
Caveats
Multiple name filters are combined together, so filling several name fields narrows the result more aggressively., Exact Date of Birth takes precedence over Birth Date From and Birth Date To when both exact and range inputs are filled., Country Code is exact, while name filters are contains-style.

Default table sort

Newer restricted-user rows appear first unless the product code sends a different sort.

Inputs
sortField, sortDirection
Transform
The read flow supports a whitelist of sortable fields and defaults to Created At descending when the UI does not expose a visible sort interaction.
Caveats
No visible column sort control was verified on the current Sanctions List page.

Exclusion reason summary-card scope

These cards explain the global valid restricted-user population by reason; they are not filtered by the table filters.

Inputs
valid restricted-user rows, exclusion reason id
Transform
Summary cards group valid restricted-user records by exclusion reason and render one card per returned reason count.
Caveats
The read response also contains total, valid, auto-generated, and manual counts, but the current UI renders only the by-reason cards., Invalid records are not counted in the by-reason cards.

Exclusion reason active count

The selector values come from the active reason catalog, while active counts describe valid records attached to each reason.

Inputs
Exclusion Reason selector, valid restricted-user rows
Transform
The exclusion-reason lookup returns reasons ordered by name and an active count based on valid restricted users for each reason.
Caveats
The current selector displays reason names; it does not show the active count beside each option.

Manual restricted-user create defaults

Add User creates a manual valid restricted-user entry; it is not an import or sanctions-source sync action.

Inputs
Full Name, First Name, Last Name, Country Code, Exclusion Reason, Date of Birth, Comment, Exclusion End Date, current admin
Transform
Creates a manual restricted-user row, derives missing first or last name from Full Name, stores a default manual comment when Comment is empty, marks the row valid, marks it non-auto-generated, and records the current admin as creator when available.
Caveats
Backend rejects an active duplicate with the same Full Name, Date of Birth, and optional Country Code., Name, country, date of birth, reason, and source are not editable later from the current Edit dialog.

Restricted-user update field scope

Edit is a limited maintenance action, not a full record editor.

Inputs
selected restricted-user row, Status, Comment, Exclusion End Date
Transform
Updates only validity, comment, and exclusion-end-date values for the selected restricted-user row.
Caveats
Auto-generated rows can only be marked invalid; other edits to auto-generated rows are rejected., The dialog shows User and Reason as context but does not submit them as editable values.

Created By display fallback

Created By may show System even when the backend row has creator details unless the response is adapted to the property the table reads.

Inputs
creator association, sysUser field
Transform
The read flow joins creator details, while the current table rendering reads a sysUser-shaped property and falls back to System when that property is absent.
Caveats
Treat Created By as a helpful display field, not as the authoritative audit trail for this page., Use audit history for precise creator/update attribution when attribution matters.

Sync force-update behavior

Start Sync refreshes auto-generated sanctions rows from the configured source, but the current portal-triggered call should not be assumed to invalidate outdated rows.

Inputs
Start Sync, forceUpdate, sanctions XML source, EU Sanctions List reason
Transform
The current portal sync call sends force update enabled; backend downloads and parses the sanctions source, creates missing auto-generated rows, reactivates matching invalid rows, updates last-checked time, and skips invalidating old auto-generated rows in that path.
Caveats
The confirmation dialog says outdated entries can be marked invalid, but the verified current call path skips invalidation because force update is enabled., Sync requires the EU Sanctions List exclusion reason to exist., Manual restricted-user entries are not changed into auto-generated entries by this sync.

Restricted-user CSV export scope

Export downloads the applied filtered result set rather than only the visible table page.

Inputs
current applied filters, CSV download flag, browser admin token
Transform
CSV export sends the applied filters to the same restricted-user read flow with CSV download enabled, page one, and a limit of 10000.
Caveats
Unsaved text in filter inputs is not exported until Apply Filters is clicked., Export is disabled while the table is loading or when the current filtered result count is zero., The export cap is 10000 rows in the current frontend request.
Columns13 topicsOpen details

ID

Internal restricted-user row identifier.

Data Type
integer

Full Name

Human-readable restricted-user name. If Full Name is empty, the UI falls back to first and last name.

Data Type
string

Country

Country code attached to the restricted-user record.

Data Type
string

Date of Birth

Birth date used for search, duplicate checks, and sanctions review.

Data Type
date

Exclusion Reason

Reason category assigned to the record. Unknown is shown when the joined reason is missing.

Data Type
string

Status

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

Data Type
enum
Visible Values
Valid, Invalid

Source

Badge showing whether the restricted-user record came from sync or manual creation.

Data Type
enum
Visible Values
Auto, Manual
Display Notes
Hidden in compact view., Hidden on smaller breakpoints outside compact view.

Comment

Operator or sync comment stored on the restricted-user row. The table truncates long text and exposes the full value in a tooltip.

Data Type
text
Display Notes
Hidden in compact view.

Exclusion End Date

End date for a non-permanent exclusion. Empty values display as Permanent.

Data Type
date
Display Notes
Hidden in compact view., Hidden on smaller breakpoints outside compact view.

Created At

Row creation timestamp displayed in UTC formatting.

Data Type
datetime
Display Notes
Hidden in compact view., Hidden on smaller breakpoints outside compact view.

Updated At

Last row update timestamp displayed in UTC formatting.

Data Type
datetime
Display Notes
Hidden in compact view., Hidden on smaller breakpoints outside compact view.

Created By

Creator name when the payload includes creator user details; otherwise the table displays System.

Data Type
string
Caveats
The backend read flow joins creator details, but the current UI reads a `sysUser` property. If the response is not adapted to that property, the table falls back to System.
Display Notes
Hidden in compact view., Hidden on smaller breakpoints outside compact view.

Actions

Opens the edit dialog for the selected restricted-user row.

Data Type
action
Filters11 topicsOpen details

General Search

Searches the lower-cased first name, last name, and full name fields.

Type
text

First Name

Restricts the list by lower-cased first name using contains-style matching.

Type
text

Last Name

Restricts the list by lower-cased last name using contains-style matching.

Type
text

Full Name

Restricts the list by lower-cased combined name using contains-style matching.

Type
text

Country Code

Restricts the list to one exact three-character country code. The UI upper-cases typed values.

Type
text

Date of Birth

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

Type
date

Birth Date From

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

Type
date

Birth Date To

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

Type
date

Exclusion Reason

Restricts the list to one exclusion reason loaded from the exclusion-reasons lookup.

Type
select
Visible Values
All, Active exclusion reason names

Status

Filters by restricted-user record validity, not by player account status.

Type
select
Visible Values
All, Valid, Invalid

Source

Filters by whether the restricted-user row was created by synchronization or manually by an operator.

Type
select
Visible Values
All, Auto-generated, Manual
Metrics2 topicsOpen details

Exclusion Reason Count

Count shown in one top summary card for one exclusion reason.

Data Type
integer
Calculation Basis
Counts valid restricted-user records grouped by exclusion reason.
Caveats
The cards are global restricted-user statistics, not counts for the currently filtered table slice., Invalid restricted-user records are excluded from these cards., Manual and auto-generated valid records are both included when they share the same exclusion reason.

Exclusion Reason

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

Data Type
string
Caveats
A reason appears only when at least one valid restricted-user record is counted for that reason.
More help

Related pages

Dashboard / Player Statistics

Rank top winners, losers, and depositors for a selected period and row limit.

Players / Activity Log

Standalone player activity history page with filters, export, map view, row details, and comment-group context.

Players / 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.

Players / Banking

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

Players / Bonus Detail

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

Players / Bonuses

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