---
schema_version: "1"
id: 9c9f58b2cf05c8ff459b2a2ebc1616994e9d28e421388b63ea978ea46aad0684
title: Overlapping Boundaries in Territory Planning
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_ovelapping_boundaries.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_ovelapping_boundaries.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 464f31a306a379eb53cbc4ed9f6abb7031909151d88ef6a1aaf6358b0dc142e4
description: Overlapping Boundaries is a feature in Territory Planning that allows a geographic boundary, such as a postal code, to be assigned to two or more areas in a live data alignment. This capability is essential for creating highly customized territory designs in dense metropolitan areas, such as New York City or London, where a single boundary can logically belong to multiple sales territories.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Overlapping Boundaries in Territory Planning

Overlapping Boundaries is a feature in Territory Planning that allows a geographic boundary, such as a postal code, to be assigned to two or more areas in a live data alignment. This capability is essential for creating highly customized territory designs in dense metropolitan areas, such as New York City or London, where a single boundary can logically belong to multiple sales territories.

### 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>

## Key Concepts and Terms

To use this feature effectively, understand how boundaries, units, and rules interact within this model:

**Boundary Overlap:** Occurs when a single boundary such as a postal code is assigned to two or more areas.

**Visual Indicator:** Overlapping boundaries are shown on the map and in the boundary legend using a hexagonal "honeycomb" pattern.

**Units Must Be Single-Assigned:** Although a boundary can be assigned to multiple areas, the units within that boundary (such as accounts or leads) can only be assigned to a single area.

**Area-Level Assignment Rules:** These rules are mandatory when boundaries overlap. They ensure units are assigned to the correct area based on criteria (e.g., industry, revenue). When you assign an overlapping boundary, assignment rules automatically run for the affected areas.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_performance_management-264-0-0-production-enus/b1f2feb4-26b8-444f-97f7-be2349869d93/images/icon_example.png)

Example

**How Unit Assignment Works with Overlap**

Consider an unassigned postal code, 90210, that contains two units: Unit A (Industry: "Tech") and Unit B (Industry: "Aerospace"). You have created two areas, Area 1 and Area 2.

Define Rules: You create an Area Rule for Area 1 where the Industry equals "Tech" OR "Aerospace." Area 2 has no rules.

Assign Boundary: You assign postal code 90210 to both Area 1 and Area 2, creating an overlapping boundary.

Unit Assignment Outcome: Both Area 1 and Area 2 own the postal code boundary. Unit A and Unit B are assigned only to Area 1 because they meet the requirements of Area 1’s assignment rule.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_performance_management-264-0-0-production-enus/b1f2feb4-26b8-444f-97f7-be2349869d93/images/icon_important.png)

Important If Area 1 did not have assignment rules, the units remain unassigned because is no defined criteria to determine their clear destination with shared boundaries.

- **[Considerations for Overlapping Boundaries](https://help.salesforce.com/s/articleView?id=sales.territory_planning_overlapping_boundaries_considerations.htm&release=264.0.0&type=5)**  
    This feature introduces dependencies and prevents the use of certain Territory Planning features.