Country and region configuration
Track settings that may change by operating market.
Country and region configuration records the settings that change after the common product layer and the Edmissa study abroad layer are already chosen.
Use this page when an agency operates in more than one market, serves students from different regions, or needs local configuration for a branch, team, or operating country.
What belongs in this layer
Country and region variations may affect:
- Lead source labels and campaign groupings.
- Application pipelines, stages, and required stage actions.
- Form fields and field options.
- Document type names and required document checklists.
- Notification wording and timing.
- Branch, location, and team assignment rules.
- Report filters and management views.
- Compliance notes that affect how users describe or collect information.
Only document approved variations. Do not add country-specific defaults until the product or operations team has confirmed them.
Recommended review order
- Start from the shared product behavior.
- Apply the Edmissa study abroad configuration.
- List the country or region differences.
- Confirm which settings are global for the agency and which are local.
- Update forms, fields, pipelines, checklists, and document types in that order.
- Review sample records before the team uses the settings for live work.
When to create separate market docs
Keep a country or region inside the global Edmissa docs when the differences are small and configuration-focused.
Create a separate market docs area when the market needs its own navigation, workflow guides, screenshots, terminology, or release cadence.