Territory Hierarchy

Question 1

Which objects support Territory Management?

Answer 1

• Account, opportunity and master/detail children of account and opportunity.
• As a best practice, keep territory hierarchy no more than 10 levels of branches.

Question 2

Under what scenarios does sharing recalculation happen?

Answer 2

• If assignment rules are changed, sharing rules using that territory as a source will be recalculated.
• When Territory membership change, any OBS using Territory as a source will be recalculated.

Question 3

Use Cases?

Describe use cases for Territory management?

Answer 3

• Multiple groups of people (multiple teams) require either read-only or read/write access to accounts.
• An additional hierarchical structure (different from the role hierarchy) is needed.
• A single user needs to hold multiple levels in the hierarchy.
• Global users (GAM – global account manager) need to see everything from the global account downward.