Territories · geographic hierarchy and access reach
Territories organize your operation as a tree, with territories inside territories, and tie people to each one. Beyond organizing, they are the basis for the territory access scope in roles and for quota and coverage planning.
Field teams rarely organize themselves by reporting line alone. They organize by area: South, Southeast, downtown, the interior. Territories exist to represent that geography inside the CRM, and to let it govern what each person can see.
Creating and nesting
- Open Settings and click Territories.
- Type the name in Territory name and click Create territory.
- To nest one, drag a territory into another on the tree at the left. To make a territory top-level, drag it to the Drop here to make the territory top-level area.
- Use the Expand and Collapse controls to move around large trees.
The name has to be at least two characters. The system refuses to put a territory inside itself and refuses any arrangement that would create a cycle, such as making a grandparent the grandchild of its own grandchild.
Assigning people
- Click the territory you want on the tree.
- Use the add button, with the plus sign, and pick the person under Select user.
- To take someone out, use the remove button, with the close sign, next to their name.
The same person can belong to more than one territory. Adding the same person twice to the same territory duplicates nothing.
Effect on access
In roles, each permission can be given the territory scope. Anyone with that scope sees the records whose owners belong to their territory and to its descendant territories as well. A manager assigned to Southeast therefore reaches everyone in downtown and the interior if those are children of Southeast.
When a person has the territory scope but is not assigned to any territory, they see only their own records. The scope never widens access by accident.
Territory planning
Under Territory planning you record, for each territory, the Quota, the Period and the Coverage notes. They are free planning fields, stored alongside the territory, that feed the territory strategy view.
Who can do what, and limits
- Creating, deleting, nesting and assigning people all require permission to manage settings.
- A territory that has subterritories cannot be deleted. Move or delete the children first.
- Deleting a territory deletes neither records nor users: it simply stops existing as a grouping, and anyone who depended on it to see records loses that reach immediately.