Considerations for Overlapping Boundaries

This feature introduces dependencies and prevents the use of certain Territory Planning features.

Required Editions

Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available for an additional cost in: Enterprise, Performance, Unlimited, and Developer Editions with Sales Planning in English only, and only if you have Web Services API enabled

Overlapping boundaries are only supported for live data alignments.

When overlapping boundaries are in focus, Optimization and Plan Scenarios are temporarily disabled.

Cloning an alignment with overlaps is unsupported.

Importing a territory model from an alignment with overlaps is disabled.

Importing boundary attributes to create overlaps is supported.

When publishing overlapping boundaries to Salesforce fields and CSV, the output uses comma-separated values (e.g., "OwnerID1, OwnerID2"). Attempting to publish to a single ID field (such as OwnerID in Salesforce) is unsupported.

Salesforce Maps Auto Assignment assumes that all shape layers included in its rules are non-overlapping. Be aware of this if you publish to Salesforce Maps and enable the option to create assignment rules.