What this module is for
NX / Countries is the operator workspace for country records used by NX restriction mapping. Operators use it to find a country, open its mapping hub, and manage which games or providers are restricted for that country.
Use this module when the question is country-specific: which game/provider restrictions apply to a country, whether a restriction is casino-managed or externally sourced, and where an operator can stage casino-scope changes.
Included units
List: country grid with search, country codes, flag, and row navigation.Detail: mapping hub for one country; it does not edit country metadata directly.Relations / Games: editable casino-scope restricted-game mapping for one country.Relations / Providers: editable casino-scope restricted-provider mapping for one country.
Common confusion
- Country detail is not an edit form in the current UI. It mainly opens mapping links.
- Restriction mapping has two scopes: casino and external. External mappings are visible but cannot be changed from these pages.
Restrictedcombines casino and external restrictions. UseRestricted (casino)when you need rows this CRM page can edit.Allowedmeans not currently restricted by the visible combined restriction state for that relation view.- Staging a checkbox change is not enough. The operator must use
Saveon the relation page for casino-scope changes to persist.