Territory Management Limits and Best Practices

Territory and Assignment Limits

The following limits apply to territories, their children, and their assignments:

• A territory can have up to 100 direct children
• An account can be in up to 250
• A user can be assigned to up to 100 territories
• There can be up to 25,000 total territories per Vault CRM instance
• A territory can have up to 100,000 assigned accounts
• A territory tree can have up to 10 levels

Best Practices

Use the following best practices when implementing Territory Management:

• Do not use multiple alignment methods in the same territory
• Territories should be as small as possible while ensuring accounts visible to end users are relevant
• Ensure territory names adhere to the following guidelines:
• Names must be unique
• Do not begin a name with 0 (zero)
• Do not include spaces, commas, or semicolons in names. This may cause errors in loads, exports, reports, maintenance, etc.
• Use a short of a territory name when possible. Territories are frequently joined together for alignment processes, so short territory names avoid size limitation errors.
• Do not inactivate records of the following objects:
• territory__v
• user_territory__v
• account_territory__v
• geography_territory__v
• assignment_rule__v
• assignment_rule_criterion__v
• tsf__v

Loading Territory Security Records

When data-loading a large number of territory security records, typically when initially setting up a Vault CRM instance, the following process should be adhered to:

• Load in all records
• Recalculate territory security once. Depending on the number of impacted records, this can take some time.
• For subsequent territory security updates, load in the records normally, enabling the appropriate triggers to run in a more targeted manner. Do not use migration mode.