Enterprise Territory Management Models and Assignment Rules

Why This Topic Matters
Enterprise Territory Management (ETM) is one of the heavier-weighted features in the Advanced Cloud Applications section of the Salesforce Advanced Administrator exam. It sits at the intersection of sales process design, record sharing, forecasting, and automation, which is exactly the kind of multi-layered knowledge the exam is designed to test. In the real world, companies with field sales teams carve their customer base into geographic, industry, or named-account territories, and they need accounts to flow into the right territory automatically, sales reps to gain access to the right records, and leadership to forecast by territory. ETM is the Salesforce answer to all of that, and a strong administrator must understand how its models, hierarchy, assignment rules, and access settings fit together. Expect at least a handful of scenario-based questions that require you to distinguish between model states, know when assignment rules run, and understand how territory membership affects record access.

What Enterprise Territory Management Is
Enterprise Territory Management is a feature (enabled by an administrator under Setup > Territory Settings) that lets an organization build one or more territory models. Each model contains a territory hierarchy made up of individual territories, each of which is classified by a required territory type. Accounts are placed into territories either manually or through account assignment rules, users are assigned to territories as members, and the system grants those users access to the accounts (and optionally the related contacts, opportunities, and cases) within their territories. Opportunities can also be assigned to territories, and Collaborative Forecasts can be configured to forecast by territory.

It is important to remember that ETM is the current version of territory management. The original (legacy) Territory Management product is no longer available to new organizations, and exam questions referencing territory management today are referring to ETM and its Territory2 family of objects.

Key Building Blocks
1. Territory Model
A territory model is the container for an entire territory structure. It represents a complete version of how the business divides its market. Models exist in one of three states:
• Planning — the sandbox state. You can build the hierarchy, create rules, assign users, and even run assignment rules to preview which accounts would land in which territories, all without affecting live record access or forecasts.
• Active — the live state. Only one model can be active at a time. In the active model, territory assignments actually grant users record access and feed territory forecasts.
• Archived — the retired state. When you activate a new model, the previously active model is automatically archived. An archived model cannot be reactivated; it can only be viewed for reference or deleted.

Edition limits matter here: Developer, Performance, and Unlimited editions allow up to four territory models (in any combination of states), while Enterprise Edition allows two. Each model can hold 1,000 territories by default, and Salesforce can raise this limit (up to 99,999) on request.

Models can be cloned. Cloning creates a new model in Planning state and copies the hierarchy, and you can choose whether to also copy assignment rules and user assignments. This is the recommended way to prepare next year's territory realignment without disrupting the current active model.

2. Territory Types
Every territory must have a territory type. Territory types are labels such as Named Accounts, Geographic, or Industry Vertical that help organize territories by their key characteristics. Each type carries a priority value. The priority is not used by account assignment rules; it is used by the opportunity territory assignment logic to break ties when an opportunity's account belongs to multiple territories.

3. Territory Hierarchy
Within a model, territories are arranged in a parent-child tree. A parent territory (for example, North America) can contain child territories (West, Central, East). The hierarchy drives rule inheritance, forecast roll-ups, and reporting. Users assigned to a parent territory do not automatically gain membership in child territories, but forecast amounts roll up the hierarchy.

4. Access Levels
At the model level, the administrator sets default access levels that territory membership grants: Account access (View, View and Edit, or View, Edit, Transfer, and Delete), plus access to Contacts, Opportunities, and Cases associated with those accounts. These defaults can be overridden on individual territories, which lets you give, for example, a strategic accounts territory more generous access than a general field territory. Territory-based access is additive to the organization-wide defaults, role hierarchy, and sharing rules; it never removes access that a user already has.

How Account Assignment Rules Work
Account assignment rules are the automation engine of ETM. A rule is a set of filter criteria evaluated against account fields, such as Billing State equals California or Industry equals Manufacturing AND Annual Revenue greater than 5,000,000. When an account matches the criteria of a rule attached to a territory, the account is assigned to that territory.

Key facts about assignment rules:
• Rules are created in the context of a territory, but an existing rule can also be assigned to additional territories, so the same logic can be reused.
• A rule has an Active checkbox. Inactive rules are ignored when rules run.
• A rule can be flagged to Apply to child territories. When this is set on a rule at a parent territory, every child territory inherits that rule. Inherited rules count toward the child's rule limit.
• Each territory can have a maximum of 15 assignment rules, including inherited ones.
• An account can be assigned to multiple territories at the same time if it matches rules in more than one territory. Rules are not mutually exclusive in the way that lead or case assignment rules are.
• Accounts can also be assigned manually from the territory's Manually Assigned Accounts related list or from the account's Assigned Territories related list. Manual assignments persist when rules are rerun; rule-based assignments are recalculated.

When Do Rules Run?
This is one of the most frequently tested details. Account assignment rules run in two situations:
• Manually, when an administrator clicks Run Assignment Rules on a territory or at the model level. In a Planning model this is a safe way to preview results; in an Active model it changes live assignments.
• Automatically on save, but only if the account page layout includes the checkbox Evaluate this account against territory rules on save and that checkbox is selected when the record is created or edited. Without this checkbox on the layout and checked, editing an account does not trigger reassignment. Automatic evaluation applies only to the active model.

Because assignment can be slow across thousands of accounts, running rules at the model level is processed asynchronously, and the administrator receives an email when the job completes.

Opportunity Territory Assignment
Opportunities are not assigned by the account rules. Instead, ETM provides an Apex-based opportunity territory assignment filter. Salesforce ships a default class (commonly referenced as OppTerrAssignDefaultLogicFilter) with this logic: if the opportunity's account is in exactly one territory, assign the opportunity to that territory; if the account is in multiple territories, assign it to the territory whose territory type has the highest priority; if there is still a tie, make no assignment. A developer can write a custom filter class and the administrator selects it in Territory Settings. Individual opportunities can be excluded from the filter by selecting the Exclude from the territory assignment filter logic checkbox, which preserves a manual territory choice on that opportunity. The filter runs when opportunities are created, and it can also be run on demand for existing records.

Users, Membership, and Forecasting
Users become members of a territory through the Assigned Users related list. A user can belong to many territories across the hierarchy, and territory membership is independent of the role hierarchy. When Collaborative Forecasts is configured to use territories, a forecast manager is designated for each territory, and forecast amounts for opportunities assigned to that territory roll up through the territory hierarchy rather than the role hierarchy.

Reporting and Visibility
ETM supplies dedicated report types once they are enabled in Territory Settings. Common ones include Accounts Assigned to Territories, Accounts Not Assigned to Territories, Users in Territories, Users Not in Territories, and Territory Model Summary. The Territory Model Summary report is especially useful before activation to validate that the planned model has the expected coverage. Chatter can also be enabled on territory records so teams can collaborate directly on territory pages.

Typical Implementation Flow
1. Enable Enterprise Territory Management and set default model access levels.
2. Create territory types with appropriate priorities.
3. Create a territory model (starts in Planning).
4. Build the territory hierarchy.
5. Define account assignment rules, marking parent rules to apply to children where appropriate.
6. Assign users to territories.
7. Run assignment rules in Planning and review with the Territory Model Summary report.
8. Add the Evaluate this account against territory rules on save checkbox to the account layout.
9. Activate the model; the previously active model is archived automatically.
10. Optionally configure the opportunity territory assignment filter and territory-based forecasting.

Exam Tips: Answering Questions on Enterprise Territory Management Models and Assignment Rules

Tip 1 — Anchor on model states. If a question describes testing, previewing, or preparing next year's structure, the answer involves the Planning state or cloning the active model. If it mentions users gaining record access or forecasts changing, the model must be Active. If it mentions reactivating an old model, recognize that archived models cannot be reactivated — the correct approach is to clone or rebuild.

Tip 2 — Remember the one-active-model rule. Any answer choice that implies two models are live simultaneously is wrong. Activation of a new model always archives the current one.

Tip 3 — Know exactly when rules fire. Rules run when an administrator runs them manually, or on account save only if the Evaluate this account against territory rules on save checkbox is on the layout and selected. If a scenario says accounts are not being reassigned after edits, the missing checkbox is the most likely answer. Do not confuse this with lead or case assignment rules, which use a different mechanism.

Tip 4 — Distinguish account rules from opportunity assignment. Account assignment rules never assign opportunities. Opportunities are handled by the Apex filter, which relies on territory type priority to break ties. If a question asks why opportunities are not being assigned when the account is in several territories, think about priorities being equal or the filter not being selected.

Tip 5 — Rule inheritance and limits. A rule marked Apply to child territories flows down the hierarchy. Each territory, including inherited rules, maxes out at 15. Questions about reducing duplicate rule maintenance usually point to creating the rule once at the parent level with inheritance, or assigning an existing rule to multiple territories.

Tip 6 — Accounts can be in many territories. Unlike many assignment features, territory assignment is not exclusive. If a scenario needs an account visible to both a geographic team and an industry team, that is expected behavior, not a problem to fix.

Tip 7 — Manual versus rule-based assignments. Manually assigned accounts stay put when rules rerun. If a question asks how to keep a strategic account in a territory regardless of criteria, manual assignment is the answer. For a single opportunity that must stay in a chosen territory, use the exclude-from-filter checkbox.

Tip 8 — Access is additive and overridable. Model-level default access can be overridden per territory, and territory access never reduces existing access. Watch for distractors suggesting that territories can restrict visibility below the organization-wide default.

Tip 9 — Use the right reports. Pre-activation validation points to the Territory Model Summary report; finding orphaned accounts points to Accounts Not Assigned to Territories; checking coverage gaps for reps points to Users Not in Territories.

Tip 10 — Watch for limit-based distractors. Remember two versus four models by edition, 1,000 territories per model by default (extendable), and 15 rules per territory. When an answer choice quotes a wildly different number, it is usually a distractor.

Tip 11 — Read for the business goal. Advanced Administrator questions often bury the technical clue inside a business story. Translate phrases such as regional sales managers need to see their team's accounts into territory membership and access levels, finance wants to forecast by region into territory-based Collaborative Forecasts, and sales operations wants to model a reorganization without disruption into cloning into a Planning model.

Mastering these distinctions — model states, the exact triggers for rule evaluation, inheritance, access behavior, and the separate opportunity logic — will let you answer nearly every Enterprise Territory Management question on the exam with confidence.