Territory
A Territory in Salesforce is a node in the Enterprise Territory Management hierarchy: a named container with assigned users, assigned accounts, child territories, and rules that decide which accounts belong inside.
Definition
A Territory in Salesforce is a node in the Enterprise Territory Management hierarchy: a named container with assigned users, assigned accounts, child territories, and rules that decide which accounts belong inside. Territories define the structure of a sales organization (Regions, Industries, Strategic Accounts, Channels) and grant the assigned users access to the accounts the territory contains. The hierarchy supports up to 1,000 territories per model and 5 levels deep, with parent territories rolling up the access of their children.
Territories are the unit of organization in Enterprise Territory Management (ETM), the modern replacement for the legacy Customizable Territory Management feature. A Territory belongs to a Territory Model (the version of the entire tree, in Active, Planning, or Archived state). Multiple models can coexist in Planning state for planning purposes, with one designated Active at any time. Activation pushes the Territory's account assignments and user access into the live sharing layer, granting the assigned users access to the accounts immediately and at scale.
How Territories structure sales organizations
What a Territory record contains
A Territory record has a Name, a Label, a Territory Type, a Parent Territory (optional, for hierarchy), and an Account Access Level (View Only, View and Edit, Transfer). Inside the territory, the admin assigns users (UserTerritory2Association records), accounts (ObjectTerritory2Association records), and rules (Territory2RuleAssociation records). The combination is what defines who has access to which accounts under what terms. The Territory itself is just the container; the relationships do the actual work.
Territory Type and consistent naming
Each Territory has a Territory Type that classifies its purpose: Geographic, Strategic Accounts, Industry, Product Line. Territory Types are admin-defined and used purely for organizational and reporting purposes. They do not change behavior. The benefit of consistent Territory Types is reporting: a regional sales VP can run a report on "all Geographic territories with quota above X" or "all Strategic Account territories in EMEA". Without consistent types, the hierarchy is queryable but not slicable.
Account Access Level: View, Edit, Transfer
Each Territory grants its assigned users a configurable access level on the assigned accounts. View Only lets users see the account but not edit. View and Edit lets users update fields. Transfer Records lets users reassign account ownership. The access level applies to all accounts in the territory uniformly. For more granular access (some users edit, some view only), use multiple territories with different access levels. The single-access-level constraint per territory is one of the practical reasons hierarchies grow.
Manual vs rule-based account assignment
Accounts can be assigned to territories two ways. Account Assignment Rules evaluate against account fields (BillingCountry = USA, Industry = Tech) and auto-assign matching accounts to the territory. Manual assignment lets a territory manager add a specific account regardless of rule matches. Manual assignments are sticky: they override rule changes and persist until explicitly removed. Most territories use rules for the bulk of accounts and manual assignment for the strategic exceptions. The ObjectTerritory2Association record tracks both modes through its IsManual field.
User assignment and territory roles
Users assigned to a territory inherit the territory's access on its accounts. The UserTerritory2Association record links the user to the territory, with an optional Role label (Account Manager, Sales Rep, Overlay, SE) for reporting. Multiple users can be assigned to the same territory, and one user can be assigned to multiple territories. A salesperson covering both Pacific Northwest and Strategic Accounts has two UserTerritory2Association rows. The union of their accounts across territories is what they can see.
Territory inheritance and the hierarchy effect
The territory hierarchy enables inheritance. A user assigned to a parent territory inherits access to every account in every child territory, recursively. This is what lets a regional VP see all accounts in the regional territories below without separate assignments. The inheritance is automatic and not opt-out. A user mistakenly assigned to a high-level territory immediately gets access to thousands of accounts, which is the most common cause of "why can my new hire see all our enterprise accounts" support tickets.
Opportunity Territory and the deal-level association
Opportunities created on an account in a territory inherit the territory assignment by default. The opportunity's Territory field is set to the territory of the parent account at creation. If the account is in multiple territories, the platform picks the first match, which is rarely what the team wants. Most ETM deployments build a Flow on Opportunity Create that picks the right territory based on Opportunity Type or other deal-level data. The default is functional but not always correct.
Creating a Territory in Enterprise Territory Management
Creating a Territory is a sequence of dependent steps: confirm the Territory Model is in Planning state, define the territory record, configure rules and manual assignments, assign users, and activate the model.
- Open the Territory Model in Planning state
Setup, Territory Models. Open the active Planning model. New territories should be added in Planning, not Active, to avoid premature sharing changes.
- Create the Territory record
Click New Territory inside the model. Set Name (Pacific Northwest), Label (display name), Parent Territory (if part of a region tree), Territory Type, Account Access Level.
- Add Account Assignment Rules
Open the territory, Assignment Rules tab, New. Define criteria (BillingState in CA, OR, WA). Mark Active. Optionally apply to child territories.
- Assign users to the territory
Territory page, Users tab, Add User. Pick the salesperson, set the optional Role label, save. Multiple users per territory are supported.
- Run assignment rules to populate accounts
Click Run Rules at the territory level. The platform evaluates the rules against all accounts and creates ObjectTerritory2Association rows for matches. Audit the count before activation.
- Add manual account assignments if needed
For strategic accounts that should belong to the territory regardless of rules, manually assign them from the Accounts tab on the territory page. The manual flag overrides future rule changes.
- Activate the Territory Model
When the territory structure and assignments are stable, activate the Territory Model. This is the irreversible step that turns on territory-based sharing org-wide.
Display name of the territory (Pacific Northwest, Strategic Accounts EMEA). Must be unique within the parent territory.
User-facing label shown in territory pickers and reports. Defaults from Name but can be customized.
Classification used for organizational and reporting purposes. Admin-defined picklist values.
View Only, View and Edit, or Transfer Records. Applies uniformly to all accounts in the territory.
The parent model this territory belongs to. Defaults to the currently open model. Cannot be changed after creation.
- A user assigned to a parent territory inherits access to every account in every child territory. The inheritance is automatic and powerful, often unintentionally granting broad access.
- Manual account assignments are sticky. They override rule changes and persist until explicitly removed. Audit the IsManual field on ObjectTerritory2Association quarterly.
- Opportunity Territory inheritance picks the first matching account territory, which may not be what the team wants. Build a Flow on Opportunity Create to set the right territory deliberately.
- Activating a Territory Model is irreversible without rebuilding. Plan the activation timing carefully, ideally during a maintenance window.
- Territories cap at 1,000 per model and 5 levels deep. Larger organizations split the territory structure across multiple models, which then needs careful coordination.
Trust & references
Cross-checked against the following references.
- Enterprise Territory Management OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Territory.
- Enterprise Territory Management OverviewSalesforce Help
- Build Territories in a ModelSalesforce Help
- Account Assignment RulesSalesforce 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. What is a Territory?
Q2. Can territories be non-geographic?
Q3. Why review territories periodically?
Discussion
Loading discussion…