The Regions and Countries module allows administrators to define business-oriented geographic groupings - such as Nordics, LATAM, DACH, or Benelux - and assign countries to them. These groupings serve as an operational filter on the Review Screen, enabling teams operating across multiple geographies to segment documents by region or country.
Regions are purely organizational constructs for filtering - they do not control user access, document visibility, or data residency.
How It Works
Region Definition
A region is a named grouping of one or more countries, created and managed by administrators.
Where Regions Are Used
Regions and countries are available as filter criteria on the Review Screen, where teams can narrow the document list by region or by a specific country. This is the only area of the platform where region groupings apply.
What Regions Do Not Control
Regions are exclusively operational filters. They do not affect:
User access or document visibility (use Self-Service Access and role-based controls for this)
Data residency or storage location (set at tenant provisioning)
Scoping hierarchy (Country scope uses the document's country, not region groupings)
Supported Configurations and Options
Configuration | Detail |
Country assignment | One or more countries per region |
Scope | Not used for access control, data residency, or rule or instruction precedence |
Other Technical Specifications
Parameter | Detail |
Access control | Admin users can create and manage regions |
Country overlap | Avoid assigning the same country to multiple regions to keep filters clean |
Region limit | No documented hard limit, but keep regions meaningful and non-overlapping |
Notes
Regions are filters only - they do not enforce access control or determine data storage location
Overlapping country assignments (same country in multiple regions) may cause confusing filter results
Country scope in Instruction Builds, Transformations, and Rejection Rules is based on the country detected on the document, not on region assignments
There is no hierarchical nesting of regions (e.g., "Europe" containing "Nordics" and "DACH" as sub-regions)
Region names should be clear and non-overlapping (e.g., use "Nordics" instead of "Northern Europe" to avoid ambiguity)