[object Object]

Turning on Territory Management is a one-way door. Once enabled, the data sharing model fundamentally changes — and you can’t disable it without losing your hierarchy. Plan it like a release, not a setting toggle.

What Territories Actually Do

Territories add a second access dimension on top of Roles. A Role says “what level of the hierarchy can you see.” A Territory says “which slice of the data, regardless of hierarchy.” A rep can belong to multiple territories and see records that match any of them.

This means a New York rep on the Enterprise team can see all NY enterprise accounts — without giving them everything in the Enterprise role or everything in NY.

The Criteria Trap

Territory assignment runs on criteria you define against Account or Deal fields. If those criteria use editable fields (like Industry or Annual_Revenue), reps can move records out of their territory by editing one field. Use stable fields where possible — Region derived from billing country is far safer than free-text industry.

Forecast Hierarchy Lives Here

Forecasts hang off the territory tree, not the role tree. If you skip thoughtful territory design and just mirror your roles, your forecasts will roll up wrong on Day 1. Sketch the forecast hierarchy first, then build territories to match.

Testing in Sandbox

Before flipping the switch:

  1. Refresh your sandbox.
  2. Define the full territory tree.
  3. Run the territory assignment rule in dry-run mode against a sample of 500 records.
  4. Spot-check 20 records with reps from each territory.

Specifically look for orphaned records (no matching territory) — these vanish from rep views the moment you go live.

Rollout Sequence

1. Announce the change 2 weeks out
2. Freeze ownership reassignments for 24h before cutover
3. Enable territories in production
4. Run the assignment rule
5. Verify forecast roll-up matches yesterday's snapshot
6. Re-open ownership changes

Step 5 is non-negotiable. Numbers off by more than 3% means rules need adjustment before you tell reps to log in.

What to Do This Week

  1. Diagram your forecast hierarchy independently of your role hierarchy.
  2. List the fields you’d use as territory criteria; flag any that are editable.
  3. Spin a sandbox refresh and run the assignment dry-run.
  4. Get sales leadership sign-off on the dry-run output before scheduling cutover.
[object Object]
Share