Loading

Troubleshoot Territory Assignment Rules in Enterprise Territory Management

Publish Date: May 11, 2026
Description

Territory assignment rules in Enterprise Territory Management (ETM) may fail to assign accounts as expected, assign accounts to unexpected territories, or stop applying after model changes. This article covers the most common root causes and their resolutions.

This article applies to Salesforce administrators troubleshooting account-to-territory assignment rule failures in the Sales Territories feature.

 

State/Country Picklist Fields Require “Contains” Operator

When State and Country picklists are enabled in your org, assignment rules that use equals as the operator for state or country fields return incomplete results. The picklist-enabled fields store values differently than free-text fields. Use contains instead of equals for state and country criteria when picklists are active.

 

Accounts with Empty Field Values Are Not Assigned

Assignment rules only assign accounts whose field values match the rule criteria. Accounts with empty or null values in the criteria fields (for example, no billing country) are skipped by rules that rely on those fields. These accounts must be updated with valid field values or assigned manually.

 

“Exclude From Territory Assignment Rules” Checkbox

Each account record has an Exclude From Territory Assignment Rules checkbox. If checked, the account is excluded from all rule-based territory assignments, even if its field values would otherwise match the rules. This checkbox must be unchecked for rules to apply to the account.

 

Multi-Picklist Field Behavior

Multi-select picklist fields behave differently from single-value picklists in assignment rule criteria. includes and excludes operators on multi-picklist fields match differently than on single-value fields, and may result in unexpected assignments or non-assignments. Test rules with multi-picklist criteria in a sandbox before activating in production.

 

Accounts Remain Shared After Territory Rule Removal

When a territory is removed from an account via rule changes, the account may still appear accessible to the territory’s users if it is also shared through other mechanisms: account teams, role hierarchy, other territories in the same model, or manual shares. Removing a territory rule does not remove all access pathways.

Resolution
Step 1: Check the assignment rule operator for state/country criteria

Go to Setup > Territory Models > [Your Model] > Rules and open each rule that filters on billing state, billing country, or similar address fields. If State and Country picklists are enabled in your org, change any equals operator to contains for these fields. Save and re-run the rules.

 

Step 2: Verify the “Exclude From Territory Assignment Rules” field on problem accounts

On the Account record, verify the Exclude From Territory Assignment Rules checkbox is unchecked. Add this field to your Account page layout if it is not visible. If the field is checked, uncheck it and re-run assignment rules to assign the account.

 

Step 3: Check for empty address or criteria fields on unassigned accounts

Run a report on Accounts with filters matching your rule criteria. Identify accounts where the criteria fields (for example, Billing Country) are blank. Update those accounts with valid values and re-run rules, or add those accounts to territories manually if they cannot be updated.

 

Step 4: Diagnose accounts that retain access after territory removal

Add the Sharing button to the Account page layout (Setup > Object Manager > Account > Page Layouts). Use the Sharing button on the account record to inspect all active sharing rules and manual shares. Identify whether the user’s remaining access is through account teams, role hierarchy, or another territory in the model, and remove those separately if needed.

 

Step 5: Re-run assignment rules after any rule changes

After modifying assignment rules, run rules from Setup > Territory Models > [Model] > Run Rules or from within the territory record to apply the updated logic. Rules do not re-apply automatically to existing accounts unless triggered by a save or a manual rule run.

Running rules from Setup assigns accounts to territories according to the rules for the Active or Planning model. Rules only trigger automatically on individual accounts when the account is saved and the “Evaluate this account against territory rules on save” setting is enabled on the page layout.

Additional Resources

My rules work correctly in the sandbox but not in production. What could be different?

The most common differences are: (1) State and Country picklists may be enabled in production but not sandbox, requiring the contains operator; (2) the production territory model may be in Active state while sandbox is in Planning state, and rules behave differently across states; (3) account data in production may have empty or differently formatted field values compared to sandbox test data.

Can I automatically assign leads to territories the same way I assign accounts?

Automated lead assignment is not supported natively in Sales Territories. Options include: using Salesforce Maps Territory Planning (add-on product) to create and publish territory models with lead assignments, or importing a CSV file of lead-to-territory assignments using Data Loader.

Can I assign an opportunity to a parent territory rather than its child territory?

By default, accounts matching multiple territories on the same hierarchy branch are assigned to the lowest-level (child) territory. To assign accounts to higher-level territories as well, uncheck the “Apply to child territories” option on the parent territory’s rules. Users must also have full access to the opportunity’s parent account to assign or select a territory on the opportunity record.

 

How Do Territory Assignment Rules Work?

Run Assignment Rules for a Territory

Why Do My Territory Assignment Rules Work Differently When Using the Excludes Criteria? (004205206)

Enable Sales Territories (000396697)

Knowledge Article Number

005321975

 
Loading
Salesforce Help | Article