Salesforce Territory Management organises accounts and opportunities into a structured territory hierarchy, assigns users to territories, and provides territory-level pipeline visibility and forecasting. It is the right tool for sales organisations that divide coverage by geography, industry, company size, or named account lists — where the role hierarchy (which controls record visibility based on the org chart) doesn’t cleanly represent how accounts should be distributed across the sales team. This guide covers Enterprise Territory Management (ETM) — the current Salesforce implementation — including territory model design, assignment rules, user access, and forecasting integration.
The best guide is the one that makes the account structure easier to understand.
A useful explanation should help the reader see where territory planning fits into the CRM.
That means the guide should focus on practical sales structure rather than abstract definitions.
For many organisations, the value is in making coverage more balanced and easier to manage.
It should also show how territories affect assignment, reporting, and team coordination.
A good guide should explain what territory management is trying to solve and why the structure matters.
That makes territory setup an important part of sales planning.
Salesforce territory management is useful because some teams sell across regions, segments, or account groups that need different coverage rules. A territory model helps organise that coverage in a more deliberate way than a flat ownership structure.
Enterprise Territory Management: Core Concepts
Enterprise Territory Management (Setup → Territories → Territory Models) uses these building blocks:
- Territory Model: the container for your entire territory structure. A Territory Model has three states — Draft (being designed, not live), Active (in use, governing account access and forecasts), and Archived (retired model, data preserved but inactive). You can have multiple Territory Models in your org but only one Active model at a time. A common use: keep the current Active model running while designing next year’s territory realignment in a Draft model, then activate when ready.
- Territory Type: a category for classifying territories — Geographic, Industry, Named Account, Channel Partner. Territory Types are labels that help admins organise territories within the model but don’t affect functionality.
- Territory: a specific territory within the model hierarchy — e.g., “Western United States,” “Financial Services,” “Enterprise Named Accounts.” Territories are arranged in a parent-child hierarchy (Americas → North America → West → Pacific Northwest).
- Territory Assignment Rules: criteria-based rules that automatically assign Account records to territories based on Account field values. A geographic territory might have a rule: State/Province CONTAINS “CA”, “OR”, “WA”, “AK” → assign to West Territory.
- User-Territory Assignments: assigning Salesforce users (sales reps and managers) to specific territories. Users inherit access to all accounts (and their related opportunities) in their assigned territories.
Territory Access Model: How It Differs from the Role Hierarchy
The role hierarchy gives managers access to records owned by users below them in the hierarchy — a vertical, org-chart-based access model. Territory Management provides horizontal access — regardless of who owns a record, if an account is in a user’s territory, that user can access it.
Example: a West Coast rep and an East Coast rep both work on accounts in the same parent account’s family (a company headquartered on the East Coast with a West Coast subsidiary). The West Coast rep needs access to the West Coast subsidiary’s Opportunity without the East Coast rep (the account owner) having to manually share it. Territory assignment grants this access automatically: the West Coast subsidiary is in the West Territory (where the West rep is assigned), so the West rep can access all its records.
Territory membership grants access to Accounts AND their related Opportunities — users in a territory see all Opportunities on accounts in that territory, regardless of the Opportunity’s owner. This is controlled by the “Grant Access Using Territory Hierarchies” Opportunity sharing option in Setup → Sharing Settings.
Designing the Territory Model
Territory Structure Patterns
Geographic territories: the most common model — regions structured by country, state/region, city, or postal code.
Global ├── Americas │ ├── North America │ │ ├── Northeast US │ │ ├── Southeast US │ │ ├── Midwest US │ │ ├── West US │ │ └── Canada │ └── Latin America ├── EMEA └── APAC
Geographic assignment rules use State/Province, Country, or Zip/Postal Code fields on the Account object to assign accounts to the correct regional territory automatically.
Industry or vertical territories: accounts are segmented by industry regardless of geography. Each industry-focused rep covers their vertical nationally or globally.
Industry Territories ├── Financial Services ├── Healthcare and Life Sciences ├── Manufacturing ├── Technology └── Retail and Consumer Goods
Assignment rules use the Account Industry field: Industry EQUALS “Financial Services” → assign to Financial Services territory.
Named account territories: a specific list of companies is assigned to a dedicated rep or team — common for enterprise sales where a small number of strategic accounts receive dedicated coverage regardless of geography or industry.
Hybrid models: many organisations combine approaches. A tiered model might have: Named Account territory (top 50 strategic accounts assigned by name), Enterprise territory by geography (accounts with Annual Revenue > $1B, segmented by region), Commercial territory by geography (accounts with Annual Revenue $100M–$1B).
Setting Up Territory Assignment Rules
- In the Territory Model, create a Territory (e.g., “West United States”)
- On the Territory, open Assignment Rules and click New
- Configure criteria: field = Billing State/Province, operator = CONTAINS, value = “CA, OR, WA, AK, HI, NV, UT, AZ, CO, ID, MT, WY, NM”
- Multiple criteria rows are combined with AND logic (an account must match all criteria rows) — to use OR logic, create separate rules
- Save and Run the rule — Salesforce evaluates all Account records against the rules and assigns matching accounts to the territory
Assignment rules run automatically when:
- A new Account is created — evaluated against all territory assignment rules immediately
- An Account field used in an assignment rule is updated — Salesforce re-evaluates the account’s territory membership
- An admin manually runs “Run Rules” on a Territory or Territory Model
Accounts not matched by any rule remain without territory assignment — a common gap in geographic models is accounts with missing or non-standard State/Province values. Audit unassigned accounts regularly and either clean the data or create catch-all territories for unmatched accounts.
Manual Territory Assignments
In addition to rule-based assignment, accounts can be manually added to territories — useful for named account models where the territory list is managed explicitly rather than by field criteria. From a Territory, open the Assigned Accounts tab and manually search for and add specific accounts.
Manual assignments persist even when assignment rules are re-run — they are not overridden by rule-based assignments. If an account is manually assigned to Territory A and a rule assigns it to Territory B, the account is in both territories.
Assigning Users to Territories
From a Territory, open the Assigned Users tab and add users. Each user can be assigned to multiple territories — a senior AE covering two geographic areas or a manager who oversees both a region and a named account tier.
When assigning users to territories, configure the Access Level for each user:
- View: read-only access to accounts and opportunities in the territory
- Edit: read-write access
- All: full access including transfer ownership
Manager roles in the territory hierarchy get visibility into sub-territory data — a manager assigned to the “North America” territory inherits access to all accounts in “Northeast US,” “Southeast US,” etc. below it, without being individually assigned to each sub-territory.
Territory-Based Forecasting
When Territory Management is active, Salesforce Forecasting can be configured to forecast by territory hierarchy rather than (or in addition to) the role hierarchy. Territory forecasts roll up from individual reps through the territory hierarchy to regional and global totals — matching the business’s commercial structure rather than the HR reporting structure.
Enable territory forecasting at Setup → Forecasts Settings → Forecast Types → Add Forecast Type → Territory → select the Territory Model. The forecast type becomes available in the Forecasts tab, with columns representing individual reps and roll-ups matching the territory hierarchy.
Territory Model Cloning for Territory Planning
A significant benefit of the Territory Model architecture: when planning a territory realignment (new fiscal year, expansion into new markets, sales team restructuring), clone the Active model to create a Draft model. Design the new territory structure in Draft mode — add territories, update assignment rules, reassign accounts, model the pipeline impact — without affecting the current Active model. When the new model is approved, activate it and archive the old one.
This enables parallel modelling of territory changes with full data context — you can report on how accounts would be distributed in the new model before committing to it.
The best territory setup is the one that matches the way the business sells. If the structure is vague, coverage becomes harder to manage.
Common Implementation Mistakes
- Building the territory model before cleaning account data: geographic assignment rules based on State/Province only work if State/Province is populated and consistent. Run a data quality audit before designing geography-based rules.
- Activating a new Territory Model without aligning Opportunity sharing: Opportunity access from territories must be enabled in Sharing Settings. Without this, users in a territory see Accounts but not related Opportunities — a common post-activation gap report.
- Not aligning territory structure with forecasting hierarchy: if the territory hierarchy doesn’t match how management reviews pipeline (by region, by VP), the territory forecast rollups won’t match management’s mental model of the business.
- Forgetting to run assignment rules after bulk data updates: if 5,000 account addresses are corrected in a data clean-up project, admins must manually trigger “Run Rules” on the Territory Model to re-evaluate territory assignments for updated records.
Conclusion
Enterprise Territory Management is the right Salesforce configuration for sales organisations with geographic, vertical, or named account segmentation that the role hierarchy doesn’t naturally represent. The territory model architecture — Draft/Active/Archived states, assignment rules, user assignments with configurable access levels — provides the flexibility to manage complex coverage models and realign territories annually without losing historical data. The forecasting integration makes territory management a complete commercial structure layer within Salesforce, enabling pipeline reporting and forecast roll-ups that match the business’s actual sales coverage model rather than its HR hierarchy.
Sources
Salesforce, Enterprise Territory Management Implementation Guide (2026)
Salesforce, Territory Management and Forecasting Setup (2026)
Salesforce Trailhead, Manage Territories with Enterprise Territory Management (2026)
Gartner, Sales Territory Planning Best Practices (2025)