Settings: Territory Access Policy
Learn how to assign territory coverage to teams and staff, choose between Off, Guided and Enforced modes, and control what happens when users work outside their area.
From Territory Maps to Working Access
The Territory Access Policy controls how the geographical territories created in Settings affect the accounts that staff can work with inside the CRM.
The policy is deliberately separate from the territory builder. This allows administrators to create and review coverage first, assign territories to teams and staff, and only then decide whether the CRM should guide behaviour or actively enforce it.
Who Can Manage Territory Policy?
Territory policy and assignments affect account visibility, so management of this section is restricted. The CRM account owner can manage it, and other roles can be given explicit territory-management permissions where required.
Policy management
Controls whether a user can change the enforcement mode, outside-territory behaviour and policy switches.
Assignment management
Controls whether a user can assign saved territories to staff teams or grant additional territory coverage directly to staff.
Off, Guided and Enforced
Off
Territories remain organisational. Territory assignments do not become the new access-control layer, making this the safest mode while the initial setup is being built.
Guided
Territories describe the staff member's preferred working area, but accounts outside it can still be opened. Direct cross-territory access can be audited when that option is enabled.
Enforced
Territory coverage becomes part of account visibility. Account lists, CRM search, reports and direct account pages use the staff member's effective territory access.
Roll out gradually
Moving through the modes in stages gives administrators time to identify coverage gaps before access is fully restricted.
What Happens Outside a User's Territory?
When Enforced mode is active, the policy decides what a user receives when an account is outside their effective geographical coverage.
Hide / deny full account
The user is not given the normal account page for an account outside their coverage.
Show safe account summary
The user can receive a restricted summary containing basic company, location and ownership information without loading contacts, notes, opportunities, documents or account activity.
Accounts Not Yet Mapped to a Territory
Some account records may not yet have enough location data to place them into a territory. The policy lets you choose how those records should behave during rollout: Full access, Summary only or No access.
When an account's coordinates are missing, the CRM can resolve its location before the normal account page is shown. Once the coordinates are available, its territory mapping is refreshed and the final access decision is made before full account content is loaded.
Important Bypasses and Inheritance Rules
CRM account owner bypass
Users marked as the CRM account owner can remain outside normal staff territory lockdown when this option is enabled.
Assigned account manager bypass
A staff member selected as an account's manager can keep full access to that account even when it sits outside their geographical territory.
Team inheritance
Staff can inherit territory coverage from their team hierarchy so coverage can be managed at team level rather than user by user.
Direct staff territory grants
Additional territories can be granted directly to an individual staff member. These direct grants are additive to inherited team coverage.
Audit Guided access
Guided mode can record direct account opens outside normal coverage, helping administrators understand real working behaviour before enforcement.
Manager delegation framework
The policy includes a framework option intended to support controlled manager subdivision and delegation workflows as territory management develops.
Assigning Territories to Staff Teams
The Teams tab lets you assign one or more saved territories to a staff team. This is usually the easiest way to manage coverage for groups of users who work in the same region.
Nearest team assignment
When team inheritance is enabled, staff inherit the nearest relevant team territory assignment in their hierarchy.
Child-team coverage
If a child team has its own territory assignment, that closer assignment becomes the inherited coverage for staff in that branch.
Direct Staff Territory Grants
The Staff tab is used when an individual needs additional coverage beyond the territory inherited from their team. Direct staff grants are added to the inherited coverage rather than replacing it.
Additional coverage
Give an individual user access to one or more extra territories without changing the whole team's assignment.
Effective coverage
The policy screen shows the territories that are effectively available to each staff member after inheritance and direct grants are combined.
Account Territory Mapping Cache
The CRM maps geocoded accounts against the saved territory polygons and stores those relationships in a coverage cache. This makes access checks much faster than recalculating every map intersection each time a user opens a page.
Live accounts
See the total number of live CRM account records considered by the coverage process.
With coordinates
See how many live accounts currently have usable latitude and longitude coordinates.
Mapped accounts
Review how many accounts have been matched to at least one saved territory.
Territory mappings
See the number of account-to-territory relationships stored in the cache.
Recommended Rollout
- Create and visually review all required territories first.
- Open Territory Access Policy and leave the policy Off.
- Assign territories to staff teams.
- Add direct staff territory grants only where additional coverage is genuinely needed.
- Review each staff member's effective coverage.
- Rebuild the account territory cache and check the Coverage Status figures.
- Switch to Guided and test real searches and account access with representative users.
- Confirm owner and assigned-account-manager bypass options match your working practices.
- Choose the required outside-territory and unmapped-account behaviour.
- Only move to Enforced once the coverage and exceptions have been tested.
Getting Territory Access Right
Test with ordinary staff accounts
Test with users who are not CRM owners so owner bypass does not hide a territory-policy issue during rollout.
Remember assigned managers
If account managers work across geographical boundaries, keep the assigned-manager bypass enabled so their own accounts remain available.
Rebuild after boundary changes
If a territory's areas are changed, rebuild the account mapping cache before using the result to judge staff access.
Watch unmapped accounts
Accounts without usable location data need careful handling because the CRM cannot make a geographical decision until their location is resolved.
Need to Change the Territory Boundaries?
Territory Access Policy controls who receives coverage. The actual geographical areas themselves are created and edited separately in Territories.