Zoho CRM Territory Management: Setup Guide, Rules and Limits for 2027

What does Zoho CRM territory management actually do?

Territory management segments your customer data into territories and sub territories, then controls who can see and edit records in each one. Records are placed in territories automatically by rule criteria when they are created or edited, and territory managers or admins can also assign them by hand.

It is a data-sharing and planning tool, not an ownership tool. A territory decides which group of users can work an account. The record owner still comes from the user who created it, an import, or an assignment rule. That distinction causes most of the confusion we see in audits.

When you enable it, Leads, Accounts, Contacts and Deals get a Territories field, and each module's home page gets a territory filter.

By default, territories are assigned from account criteria, and contacts and deals follow their account. Two optional settings, the Lead Territory Rule and the Deal Territory Rule, let you give leads and deals their own criteria. That matters when one account buys across regions, for example a global customer whose US and UK offices each run deals with the local team.

Which editions include territory management, and what are the limits?

Zoho's comparison page lists territory management on Enterprise and Ultimate only. Only users with the Administrator profile can enable it. The other rules below come from Zoho's help pages.

Check current limits on Zoho's comparison page before you plan a large hierarchy, because Zoho revises them. Our guide to Zoho CRM editions explains what else changes when you move up to Enterprise.

Should you build territories from scratch or extend your role hierarchy?

When you click Get Started, Zoho asks you to choose one of two options, and the choice cannot be reversed. Read Zoho's decision guide first, then use this table.

How do you set up Zoho CRM territory management step by step?

Agree the territory map with sales leadership before anyone touches Setup. One clear field, such as Billing Country or Region, makes rules easier to test. Then follow these steps.

1. 1Go to Setup > Security Control > Territory Management and click Get Started.
2. 2Choose Extend from Role Hierarchy or Start from Scratch.
3. 3Under Territories, click Create New Territory. Enter a Name and Description, choose a Territory Manager and a Parent Territory.
4. 4Add Users and set their permission for the territory's records: Read Only or Read/Write/Delete.
5. 5Under Territory Rules, set the account criteria, for example Billing Country is Canada.
6. 6If deals or leads need their own criteria, open the more (...) menu, select Settings and enable the Deal Territory Rule or Lead Territory Rule, then add those rules to each territory.
7. 7Create sub territories from the Territory Hierarchy page using the Create Child Territory icon.
8. 8Go to Assign Territories and run the rules for existing accounts, and for deals if deal rules are on.
9. 9Log in as a test user in each territory and confirm what they can see and edit.

Once rules are live, build a simple report of accounts with no territory and review it weekly. Records with blank or misspelled country values are the usual cause, so a picklist for Billing Country, or a validation step on web forms, prevents most gaps. Territory options can also be used in report criteria, which makes regional pipeline reports easy to share with each manager.

How do territories decide who can see and edit records?

Access is the combination of two things: the module permissions in the user's profile and the permission the territory gives its users. A user can edit a territory record only if the profile allows editing that module and the territory gives Read/Write/Delete, or the user is that territory's manager. Owners keep full access to their own records, child records follow the parent record, and administrators see everything.

Deals follow their contact first, then their account. If the contact on a deal has no territory, Zoho checks the account. With the deal rule enabled, the deal is also checked against each territory's deal criteria.

A worked example: a hierarchy of Global, then North America and EMEA, then USA East, USA West and Canada under North America, and UK and UAE under EMEA. An account with Billing Country United Kingdom must match EMEA's criteria before it can join UK. Keep parent criteria broad, such as a list of countries, and child criteria narrow.

How do territories connect to assignment rules and forecasts?

Use assignment rules for ownership and territories for visibility and planning. A common pattern is a Deals assignment rule with one entry per region, using round robin among that region's reps, plus a catch-all entry. Our answer on assigning deals by territory walks through that rule.

With territory management on, you can build forecasts on the territory hierarchy. Territory managers act as forecast managers and set targets for their territories and sub territories. A user who belongs to several territories can have a separate target in each one.

Be careful before you switch the feature off. Zoho says disabling it hides territory information and permanently deletes forecasts built on the territory hierarchy. If you enable it again, the territory structure itself is kept.

What mistakes should you avoid, and how can Flowpeak help?

Flowpeak is a registered Zoho partner with Zoho-certified consultants, working remotely from Chennai for teams worldwide. We design territories, sharing rules, assignment workflows and territory forecasts together, test them with real user logins, and document the rules. Zoho CRM setups start from USD 500 at a fixed price in writing, paid by milestone.

• Using territories to set record owners, then wondering why owners do not change.
• Overlapping criteria that put accounts in several territories without meaning to.
• Child criteria that do not fit inside the parent criteria, so records never reach sub territories.
• Forgetting to run rules for existing accounts after setup.
• Building 40 territories when six would do. Every territory needs a manager and upkeep.
• Leaving territory managers unset, so access requests and target setting fall back to one busy parent manager.

Frequently asked questions