Getting started

Your first territory model, in about ten minutes. This page assumes Territory Mapper is installed and configured. If it is not, or if you are not sure, start at Admin setup — four of the setup steps cannot be shipped with the package and have to be done by hand in your org.

Before you start: one thing that must already be true

Salesforce geocoding clean rules must be enabled and running in this org.

Territory Mapper assigns a record to a territory by testing the record's latitude and longitude against territory boundaries. Salesforce populates those coordinates; Territory Mapper never calculates them. If clean rules are off, your records have no coordinates, nothing is assigned, and the map still looks perfectly healthy.

This is the single most common cause of "I set everything up and nothing happened". Check it now — it takes two minutes.

1. Open Territory Mapper

App Launcher → Territory Mapper. The app opens on the map, with the territory tree on the left.

If you land on an empty grey panel instead of a map, go to Troubleshooting.

2. Create a territory model

A territory model is a named container for one complete set of territories — "Sales", "Service", "FY27 Plan". An org can hold several at once, and two models may cover the same ground without conflicting: they never see each other.

1. In the territory tree, choose Add new territory model.
2. Give it a name and a description.

You now have a model with nothing in it.

3. Add your first territory

1. Select the model, then Add new territory.
2. Name it. Names are yours — there is no fixed set of tiers and no required naming.
3. Save.

The territory exists but has no boundary yet. It draws nothing on the map until you give it one.

The tree on the left, the map on the right. One model, one tree.

4. Draw its boundary

Select the territory in the tree, turn on selection mode, and click areas on the map. Each click adds one census area to the selection; clicking a selected area again removes it. Shift-drag selects a rectangle.

The zoom decides how fine your selection is. Zoomed out you are picking states; zoomed in you are picking counties, then tracts, then block groups. That is deliberate, and it is explained in The two hierarchies.

When the selection looks right, Save.

Saving takes effect immediately. There is no draft, no publish step and no preview. The boundary is live in every model state the moment you save it.

5. Add a child territory

Select your territory, then Add new territory again — the new one is created beneath it. Draw its boundary the same way.

You now have a two-tier model. Repeat as deep as you need; there is no fixed limit.

6. Assign someone to it

Open the territory and add users, each with a role. A role is what someone does in that territory — Manager, Sales, Operations. See Roles and assignment.

7. Check what got assigned

Records assign themselves. When Salesforce geocodes a record, Territory Mapper tests its point against your boundaries and writes the assignment.

Two places to look:

• The record — its territory associations.
• Assignment Exceptions — every record that could not be assigned, and why. It is a work queue, not an error log; see The exception queue.

What to read next

Three things Territory Mapper does not do

Stated here because each one is a reasonable thing to assume.

1. Editing a boundary does not re-assign anything. Records assigned under the old boundary stay where they are until they are re-processed. See The exception queue.
2. There is no draft or published state for a boundary. A saved boundary is live.
3. If two territories claim the same area, the second one wins and the first shrinks. Nothing is rejected and nobody is warned. See Editing boundaries.