Salesforce Territory Assignment Rules for Account Assignment and Account Owner Routing
A batch of new accounts comes in from a trade show list on Monday. One of them is an Ohio manufacturer with 800 employees, and your territory model says that is Central Mid-Market. By Tuesday the account shows the right territory and four reps can open it, but the owner is still the integration user who loaded the list. Nobody calls it, because everyone in the territory assumes someone else has it.
In short
Salesforce territory assignment rules put accounts into territories in Sales Territories, the feature formerly called Enterprise Territory Management. Each rule holds up to 10 filter criteria and a territory can use up to 15 rules. Rules run on account create or edit only when the territory model is Active and the save carries the right flag: the Evaluate this account against territory rules on save checkbox in the UI, the AssignmentRuleHeader on API updates, or the insert setting in Territory Settings for new accounts. Rules grant access to everyone in the territory. Salesforce states that Sales Territories does not automatically assign or change account owners, and leads can only be placed in territories by hand. Assigner adds the missing step: it picks one available rep inside the matched territory, sets the owner and records why.
Why it fits
This page is for a Salesforce admin or sales operations lead running Sales Territories (Enterprise Territory Management) whose accounts land in the right territory but with the wrong owner, an integration user as owner, or no single rep accountable, and who needs every new or realigned account owned by one available rep with a recorded reason.
A territory is not an owner
Trailhead says it directly: Sales Territories does not automatically assign or change account owners. Rules decide which territory an account belongs to and who can see it. The Account Owner field stays whatever it was when the record was created or imported.
Rules are for accounts only
Assignment rules evaluate accounts. Since Winter 23 you can place leads in territories, but only manually, through Salesforce Maps Territory Planning or a CSV import. Opportunities get their territory from an Apex filter class, not from rules.
Three switches decide whether a save runs the rules
A UI edit needs Evaluate this account against territory rules on save. An API update needs the AssignmentRuleHeader. A new account needs Run territory assignment rules during account inserts in Territory Settings. Miss one and the account saves with no territory, without any error.
10 criteria per rule, 15 rules per territory
Trailhead caps a rule at 10 filter criteria and recommends 6 or fewer. A territory can have up to 15 rules, and Apply to child territories lets one rule cover a whole branch of the hierarchy, which is also how one wrong rule spreads.
Running the rules locks the model
Run Assignment Rules on the model, or Run Rules on one territory, is asynchronous and can take a long time on a large org. You cannot modify a territory until the completion email arrives, so realignment day means a frozen model.
Every owner needs a reason
When a rep asks why a colleague got the Fortune 1000 account in their region, native territory management has no answer, because it never chose an owner. Assigner records the rule, rotation position, load and availability behind each owner it sets.
Side by side
When Salesforce territory assignment rules fire, and what they leave undone
| How the account changes | What must be true for rules to run | What happens if it is not | Sets the account owner | Explains the choice |
|---|---|---|---|---|
| Created in the UI | Run territory assignment rules during account inserts is selected, the model is Active, the rule is Active and assigned to a territory | The account saves with no territory | No | No |
| Edited in the UI | Evaluate this account against territory rules on save is selected | The old territory stays even if the account moved state or segment | No | No |
| Updated through the API, Data Loader or an integration | The call specifies the AssignmentRuleHeader | Integration updates skip the rules silently | No | No |
| Run Assignment Rules or Run Rules | Started by an admin, optionally filtered by date range or one field | Nothing runs until someone starts it, and the model is locked until the email | No | No |
| Account listed in Territory2ObjectExclusion | Nothing, by design | The account is skipped even when it meets the criteria | No | No |
| Assigner beside Salesforce | The account has a territory, set by your rules or by Salesforce | Unowned accounts surface in a queue with the reason they were not assigned | Yes, one available rep in the territory | Yes, on every assignment |
Sources: Salesforce Sales Territories Implementation Guide (Spring 26 and Winter 23 editions), Salesforce Object Reference Spring 26, Winter 23 release notes, the Trailhead module Advanced Territory Management, and Salesforce Help on assigning accounts by rules. Confirm in your own org, because settings and page layouts change the behavior.
In detail
How territory assignment rules behave in a real Salesforce org
Why accounts get a territory and keep the wrong owner
Territory management answers a coverage question: which group of sellers is responsible for this account, and who may see and edit it. It does not answer the ownership question. Trailhead puts it plainly: Sales Territories does not automatically assign or change account owners. Assigning an account to a territory gives every user in that territory access at the level the territory defines, Read Only, Read/Write or Owner, and that is all.

So the owner field keeps whatever value it had. For imported lists that is often the integration user or the admin who ran the load. For accounts converted from leads it is the lead owner, who may sit in a different region. Trailhead lists the two workarounds teams use: set a placeholder user as owner and let territory access do the work, or use Apex or another programmatic resource to designate an assigned territory user as the account owner. A long running Trailblazer Community thread on why territory management does not change account ownership ends the same way, with a batch job that periodically updates ownership.
Both workarounds carry a cost. The placeholder owner breaks every report, email alert and assignment rule that keys on Account Owner. The batch job needs a rule for picking one person when a territory has four reps, and that is the decision nobody wrote down.
When territory assignment rules run, and when they quietly do not
Rules fire on account creation or update only if the territory model is in the Active state. On top of that, each path into the account has its own switch.
- UI edits run the rules only when Evaluate this account against territory rules on save is selected. If the checkbox is not on the page layout, or defaults to unchecked, users can change an account billing state from Ohio to Texas and it stays in Central.
- API updates, which includes Data Loader, middleware and most enrichment tools, run the rules only when the call specifies the AssignmentRuleHeader.
- New accounts run the rules only when Run territory assignment rules during account inserts is selected in Territory Settings.
For everything else there are two manual actions. Run Rules on a single territory, and Run Assignment Rules on the whole model. You can scope a run to a last modified date range or to one field filter, though reference fields and picklist values are not available as run filters. Runs are asynchronous, Salesforce warns they can take a long time, and you cannot modify a territory until the completion email arrives.
Salesforce territory assignment rules not working, the checklist
When an account ends up in no territory or the wrong one, work through these in order. Each one appears in the Salesforce documentation, and each one fails without an error.
- The model is not Active. Rules in a Planning model only preview assignments.
- The rule is inactive or not assigned to a territory. A rule must be Active to run on create or update, and it does nothing until it is linked to at least one territory.
- The save did not carry the flag. The UI checkbox, the API header or the insert setting, as above.
- The account is excluded. A Territory2ObjectExclusion record keeps an account out of rule runs even when it meets the criteria.
- State and country picklists are on. Salesforce Help says rules on those fields must use contains matching instead of equals matching.
- A ZIP code range compares as text. Help gives the example that 9 is higher than 80000, so a range rule on postal codes catches the wrong accounts.
- The rule author cannot see the field. The fields available for account assignment rules depend on field level security for the person building the rule.
- A run is still in progress. Until the email arrives, the assignment you are checking may not exist yet.
If all eight pass and the territory is right, the remaining complaint is usually ownership, which is the subject of the first section and not a rule failure at all.
Limits that shape a territory model
A few numbers decide how far a rule based model can stretch before it needs code or a second tool.
- 10 filter criteria per rule. Trailhead recommends sticking to 6 or fewer, and filter logic such as (1 AND 2) OR 3 is supported.
- 15 rules per territory. Select up to 15 rules on a territory; use Apply to child territories to let a parent rule cover its descendants.
- One active model. Only one territory model can be Active at a time, and archived models cannot be reactivated.
- Models per org. Enterprise Edition allows 2 models, Performance, Unlimited and Developer allow 4, and clones count.
- Territories per model. The Winter 23 guide lists 1,000 territories per model on Enterprise and Developer, with up to 99,999 on Performance and Unlimited through Salesforce Support. Check your edition before you plan a ZIP level model.
None of these limits counts reps. A territory can hold as many users as you like, and Trailhead suggests roughly three territories to one user as a planning ratio. That is where coverage and ownership drift apart: the more users per territory, the less a territory assignment tells anyone who should pick up the phone.
Leads and opportunities in a territory model
Leads. Winter 23 made it generally available to manage coverage for leads that you assign manually to territories. There is no rule based lead assignment. Bulk options are Salesforce Maps Territory Planning, a paid add-on, or a CSV import through Data Loader, and lead access is set with Turn on Lead Access. Inbound leads still need lead assignment rules or another router to get an owner, which is covered on our page about Salesforce lead routing.
Opportunities. An opportunity holds one territory in a single Territory field. Filter based opportunity territory assignment uses an Apex class that implements the OpportunityTerritory2AssignmentFilter interface; Salesforce ships sample logic, and you start it with Run Opportunity Filter or set it to run when opportunities are created. Users can tick Exclude from the territory assignment filter logic on a record. Archiving a model blanks the Territory field on opportunities and deletes territory forecasts and quotas, which is worth knowing before an annual realignment. Opportunity ownership has the same gap as accounts, and our page on Salesforce opportunity assignment covers the options.
Which Salesforce editions include territory assignment rules
The implementation guide lists Sales Territories in Performance and Developer Editions and in Enterprise and Unlimited Editions with Sales Cloud. On the current Sales Cloud pricing page, Sales Territories is marked included on Core at $195, Advanced at $395 and Max at $550 per user per month, and not included on Free, Starter Suite at $25 or Pro Suite at $100. A team on Pro Suite that wants rule based territories is therefore looking at a $95 per user per month step, or $11,400 a year for 10 users. Our breakdown of the Salesforce territory management license works through that upgrade in detail.
Before paying for it, ask what you need the model for. If the goal is forecasting and quotas by territory, Sales Territories is the native tool and worth the edition. If the goal is that every new account gets one owner in the right region, territory rules alone will not do it on any edition.
How Assigner sets the owner inside each territory
Assigner sits beside Salesforce and decides who owns each new or realigned account. Your territory model keeps deciding where the account belongs, and keeps doing forecasts, quotas and access. Assigner reads the account, uses its territory as the pool, and writes one owner back.
- Rotation inside the territory. Round robin or weighted round robin across the reps in that territory, so a senior AE can take two accounts for every one a new rep gets.
- Load counted the way you count it. Open accounts, open opportunities or new accounts this month per rep, so a rep already holding thirty fresh accounts is skipped.
- Availability. Reps who are out or at their cap are skipped, and if nobody in the territory is available, the account goes to a fallback you name instead of staying with the integration user.
- A reason on every owner. Each assignment records the territory, the rule, the rotation position and the load at that moment.
Territory rules and weighted round robin are on the Business plan at $36 per user per month billed yearly, and simple round robin with capacity caps starts on Starter at $7, both with a 5 user minimum. You license the reps who receive accounts. Assigner does not replace your territory model, Salesforce Maps or territory forecasting, and it does not guarantee coverage targets.
Questions buyers ask
Frequently asked questions
What are territory assignment rules in Salesforce?
They are rules in Sales Territories, formerly Enterprise Territory Management, that assign accounts to territories based on account field criteria such as billing state, industry or employee count. Each rule can hold up to 10 filter criteria, a territory can use up to 15 rules, and a rule can apply to child territories.
How do I run territory assignment rules in Salesforce?
Open the territory model and use Run Assignment Rules to evaluate every account, or open one territory and use Run Rules. You can limit a run to a last modified date range or one field filter. The run is asynchronous, and Salesforce emails you when it completes; until then you cannot modify a territory.
Why are my Salesforce territory assignment rules not working?
The usual causes are a model that is not Active, a rule that is inactive or not assigned to a territory, a save without the Evaluate on save checkbox or the API AssignmentRuleHeader, an excluded account, equals matching on state and country picklists instead of contains, or ZIP ranges that compare as text.
How do I exclude an account from territory assignment rules?
Salesforce stores exclusions as Territory2ObjectExclusion records, available from API version 54.0, which keep an account out of assignment rule runs even when it meets the criteria. Opportunities have a separate checkbox, Exclude from the territory assignment filter logic, on the record.
Do Salesforce territory assignment rules change the account owner?
No. Salesforce states that Sales Territories does not automatically assign or change account owners. Rules place the account in a territory and grant access to the users in it. Teams that want an owner set use Apex, a scheduled batch job, or a routing tool such as Assigner.
Can territory assignment rules assign leads in Salesforce?
No. Assignment rules evaluate accounts only. Since Winter 23 you can assign leads to territories manually, or in bulk with Salesforce Maps Territory Planning or a Data Loader import. Inbound lead ownership still comes from lead assignment rules or a separate router.
How many assignment rules can a Salesforce territory have?
Up to 15. The implementation guide says to select the checkbox for as many as 15 rules you want to assign to the territory. Each rule is limited to 10 filter criteria, and Trailhead recommends 6 or fewer to keep rules maintainable.
Are territory assignment rules the same as account assignment rules?
Effectively yes. Salesforce has native assignment rules for leads and cases only, so there is no separate Account Assignment Rules page in Setup. Territory assignment rules are the native way to assign accounts by criteria, but they assign a territory rather than an owner.
Do territory assignment rules run when I update accounts with Data Loader?
Only if the update call specifies the AssignmentRuleHeader. For inserts, the Run territory assignment rules during account inserts setting must be on. Otherwise imported or updated accounts keep their old territory until an admin runs the rules manually.
Which Salesforce edition includes territory management?
Sales Territories is available in Enterprise and Unlimited Editions with Sales Cloud, Performance and Developer. On the current pricing page it is included on Core at $195, Advanced at $395 and Max at $550 per user per month, and not on Starter Suite or Pro Suite.
How do territory assignment rules work with child territories?
When you create a rule on a territory you can select Apply to child territories, which makes it an inherited rule that also acts on every territory below it in the hierarchy. It saves rule maintenance, but one wrong criterion then affects the whole branch.
How much does Assigner cost for territory based account routing?
Territory rules and weighted round robin are on the Business plan at $36 per user per month billed yearly. Round robin with capacity caps starts on Starter at $7. Both have a 5 user minimum, and you license only the reps who receive accounts.
Keep reading
More Salesforce routing pages for sales teams:
- Salesforce territory management license - Which editions include Sales Territories and what the upgrade costs.
- Salesforce opportunity assignment - No native opportunity rules, and how teams assign deals fairly.
- Salesforce lead routing - Getting inbound leads to the right rep before territory rules ever apply.
- Lead assignment rules compared across CRMs - How Salesforce, HubSpot, Dynamics and Zoho assign leads natively.
- Salesforce round robin - Rotating leads and records across reps in Salesforce.
- Territory routing in Assigner - Route by region, segment or named account, then pick one available rep.
- Territory based lead routing - When territories beat round robin for lead distribution, and when they do not.
Stop hand-sorting your incoming work
Let Assigner route it to the right available person by skill, workload, and availability, using rules you control. Nothing sits unassigned and no one gets cherry-picked. Every assignment shows why.