What this page does
This page opens one country record and acts as the navigation hub for country restriction mappings. Operators usually reach it from NX / Countries / List after finding a country by name or code.
The page itself does not edit country metadata. Its main job is to keep the selected country context and route the operator into the editable restriction mapping pages for games and providers.
Visible sections
- The header shows the country name.
- The
Mappingstab links toRestricted ProvidersandRestricted Games.
When to use it
Use this page when the question is about restrictions for one specific country. Open Restricted Providers to review or change provider-level restrictions. Open Restricted Games to review or change game-level restrictions.
This is also the right place to start when support asks why a provider or game is blocked for a country. The detail page confirms the country context; the relation page shows whether the block comes from casino-scope rules or external-scope rules.
Important behavior
- There is no country edit form on this page in the current UI.
- The page reads country detail data so the title and mapping paths can be built.
- Actual restriction changes happen on the provider/game mapping pages.
Common confusion
Detailmeans "country workspace", not "country edit form".- Opening a country record does not by itself mean every game or provider is blocked there. The relation pages show the actual restriction rows.
- Country restriction relation pages include casino-scope and external-scope concepts. Casino-scope rows are the ones operators can stage and save from the current CRM pages.
- External restrictions can be visible in the relation views, but the current CRM pages do not let operators edit external-scope mappings there.