Before you create and use account assignment rules, make sure that you review how they work.
Required Editions
| Available in: Salesforce Classic for some features and Lightning Experience for all features |
| Available in: Performance and Developer Editions and in Enterprise and Unlimited Editions with Sales |
- A territory can have inherited account assignment rules, meaning that the rules were created somewhere higher in the territory hierarchy and also impact the given territory.
- A territory can have locally defined account assignment rules, meaning that the rule was associated at the given territory.
- If a territory doesn't have any inherited or locally defined account assignment rules, then it only contains accounts that were associated manually.
- If an account matches all inherited and locally defined account assignment rules for multiple territories on the same branch of the hierarchy, the account is assigned to the lowest matching territory.
- If a territory has multiple locally defined account assignment rules, an account is assigned to the territory only if it matches all locally defined account assignment rules on the territory.
- When referring to picklist values in your account assignment rules, specify the API name instead of its corresponding value. That way, your account assignment rules reflect any updates to picklist values. For example, you refer to the picklist API name Agriculture_Sales. You change its corresponding value from Agriculture Sales to Agriculture. Account assignment rules now reflect Agriculture.
Example
- Territory A has four rules marked “Apply to child territories“ and is a
parent of territory B.
- Territory B has three rules not marked “Apply to child territories”
and is a parent of territory C.
- Territory C has two rules.
- Territory B has three rules not marked “Apply to child territories”
and is a parent of territory C.