---
schema_version: "1"
id: e1e2ff29c0144a1ef7857c43c32c2e5c4d8188f3d446eb048d0728f58fdbc438
title: Considerations for Overlapping Boundaries
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_overlapping_boundaries_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_overlapping_boundaries_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: cd6a5bd51fed28824877b8e40ab8bd4e8f5561fbe8067745210a23f6562d6a9b
description: This feature introduces dependencies and prevents the use of certain Territory Planning features.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Considerations for Overlapping Boundaries

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

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available for an additional cost in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Sales Planning in English only, and only if you have Web Services API enabled</td></tr></tbody></table>

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.