Account Assignment Rule
An Account Assignment Rule is the territory-management mechanism that automatically associates Accounts with one or more Territories based on rule criteria.
Definition
An Account Assignment Rule is the territory-management mechanism that automatically associates Accounts with one or more Territories based on rule criteria. It is part of the Enterprise Territory Management feature, the modern replacement for the legacy Customizable Territory Management module. The rule evaluates Account fields (Industry, BillingCountry, AnnualRevenue, custom fields) against an ordered list of conditions, and assigns matching accounts to the territory the rule belongs to.
Account assignment rules sit between two concepts often confused: territory models and territories. A Territory Model is the active or planning version of the entire territory tree. A Territory is a node inside the model, with its own users, account assignments, and child territories. An Account Assignment Rule is attached to a single territory and runs when the territory model is activated or when an account is created or edited. The rule is the bridge between the data (accounts) and the structure (territories), without which territory management is just an org chart with no records inside it.
How Account Assignment Rules actually map accounts to territories
Enterprise Territory Management vs the legacy module
Two territory products have existed in Salesforce. The legacy Customizable Territory Management (CTM) was the original, dating to the early 2010s. It worked but was rigid: one territory model at a time, manual rule recalc, brittle integrations. Enterprise Territory Management (ETM), introduced in 2014, is the supported model now. It supports multiple territory models simultaneously (one Active, others in Planning), territory hierarchies up to 1,000 nodes, and rule-driven account assignment. New orgs cannot enable CTM, and existing CTM customers have migrated or are stuck on a maintenance plan.
Rule structure: criteria, logic, and inheritance
An assignment rule has up to 10 criteria (field-operator-value triples). Multiple criteria default to AND logic, but the rule can override with custom Boolean logic like (1 AND 2) OR 3. Rules can be marked Inherited, meaning the rule applies to the territory's children as well. Inheritance is what lets a parent region rule like "Country = USA" automatically assign accounts to every territory under USA. The trade-off is that complex rule trees become hard to audit. Salesforce limits a model to 5 levels of territory hierarchy for exactly this reason.
When rules run: activation, edit, and apply-rules
Account assignment rules run at three triggers. First, when the territory model is activated, the platform evaluates all rules across all accounts. Second, when an account is created or edited, the platform re-runs rules that reference the changed fields. Third, an admin can explicitly hit Run Rules on a territory to re-evaluate without waiting for an activation cycle. The first run on a 200,000-account org can take hours. The platform schedules it asynchronously and surfaces progress through the Territory Model status page.
Multiple territories per account
An account can be assigned to multiple territories if multiple rules match. This is unusual in territory products and useful in real organizations where a strategic account spans regions or product lines. The platform tracks each assignment as an ObjectTerritory2Association row, which is queryable through SOQL. Opportunities created on the account inherit the territory through default rules, but the inheritance is configurable. Most orgs lock down the override to prevent salespeople from reassigning their own deals.
Manual exceptions vs rule-driven assignment
Rules are the default, but admins and territory managers can manually assign accounts to territories, overriding the rule. The override is sticky: a manually assigned account stays in its territory even if the rule no longer matches. This is useful for strategic accounts that should not move when their industry classification changes, and dangerous when an admin forgets to clear the override after a rule update. The Manual Account Assignment report is the cleanup tool. Run it quarterly.
Sharing implications of territory assignment
When an account is assigned to a territory, the territory users gain access to the account through Territory-based Sharing. The sharing is automatic, fast, and survives rule changes. It is also the most common reason for unexpected access. A user added to a territory in the model inherits sharing for every account in that territory, immediately, without admin action. Audit territory membership at every quarterly review. The TerritoryUser report tells you who has territory-driven access right now.
Permissions and the territory-management user
Two permissions matter. Manage Territories grants the ability to build models, add territories, and write rules. Run Assignment Rules grants the ability to trigger re-evaluation. Both are profile-level permissions, gated by the View All Data or Manage Sharing permission set in most orgs. Standard users do not see territory management at all unless they have a territory user license or are listed in territory membership. The license is included in Enterprise Edition and above but counted separately from the Salesforce user license.
Creating an Account Assignment Rule on a territory
Building an account assignment rule requires Enterprise Territory Management enabled, a territory model in Planning state, and a clear set of criteria for which accounts belong in the territory.
- Enable Enterprise Territory Management
Setup, Territory Settings, Enable Enterprise Territory Management. The feature is on by default in new orgs created after 2017, but older orgs may need to flip the switch. The enable is one-way.
- Create or open a Territory Model
Setup, Territory Models, New. Give the model a name and Planning state. Models in Planning do not affect sharing. Activation is the irreversible step that pushes the model live.
- Build the territory hierarchy
Inside the model, add territories as parent and child nodes: North America, then USA, then East Region, then Northeast. Five levels is the platform maximum. Each territory has a name, label, and territory type.
- Add an account assignment rule
Open the territory, Assignment Rules tab, New. Give the rule a name, set Active = true, add criteria (BillingCountry = USA, Industry = Manufacturing), and optionally check Apply to Child Territories.
- Run rules on the territory
From the territory page, click Run Rules. The platform evaluates the rules against all accounts and creates ObjectTerritory2Association rows for matches. For new models, run rules at the model level instead.
- Activate the model
Once the rules are stable and the assignments look correct, Activate the model. This is the step that turns on Territory-based Sharing across the org. Plan a maintenance window for any model with more than 50,000 accounts.
Toggle on the rule itself. Inactive rules do not evaluate even when their parent model is active. Use this for staged rollouts.
When checked, the rule cascades to every territory under this one. Useful for region-level criteria that apply to all sub-territories.
Up to 10 field-operator-value triples. Default AND logic, with optional custom Boolean expression for OR combinations.
String like (1 AND 2) OR 3 that overrides the default AND logic on the criteria. Validate carefully - parser errors silently make the rule never match.
Planning, Active, or Archived. Only Active models drive sharing. Planning models hold the proposed structure without affecting the live org.
- Running rules on a model with 100,000+ accounts takes hours and runs asynchronously. Plan for the wait and watch the progress through the Territory Model status page.
- Manual account assignments override rule matches. A previously hand-assigned account does not get reassigned even when its rule no longer matches. Run the Manual Assignment report periodically.
- Inherited rules cascade to every child territory. A region-level rule with broad criteria can over-assign accounts unintentionally. Test rules in Planning state before activating the model.
- Territory-based sharing is automatic. Adding a user to a territory grants access to every account in that territory. There is no per-account override at the user level.
- The legacy Customizable Territory Management (CTM) module is not the same as ETM. Migrating from CTM to ETM is a one-way conversion with manual rule rewrites.
Trust & references
Cross-checked against the following references.
- Enterprise Territory Management OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Account Assignment Rule.
- Enterprise Territory Management OverviewSalesforce Help
- Define Assignment Rules for TerritoriesSalesforce Help
- Territory ModelsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Account Assignment Rules are used within which Salesforce feature?
Q2. What triggers an Account Assignment Rule to evaluate an Account?
Q3. Why is it recommended to test rule changes in a planning territory model first?
Discussion
Loading discussion…