Roles Roll Up, Territories Reach Across.

A sales director once told me she had fixed the visibility problem three times. Each time a rep could not see an account she needed, the director edited the role hierarchy, and each time the forecast broke, because the hierarchy is also what the forecast rolls up. She was using an org chart to solve a market problem. Zoho CRM has a separate tool for the market problem, and this video is about the one question that tells you which tool you need. Everything on screen is a mock demo of Zoho CRM with sample data: an invented company, invented reps and invented accounts.

Start with roles, because every Zoho CRM org has them. The role hierarchy is the org chart drawn in the system: a sales director at the top, two regional managers under her, three reps under each manager. Visibility follows the lines. The director sees everything her managers' reps own. A manager sees what his reps own. A rep sees her own accounts and, by default, nobody else's; two reps under the same manager are blind to each other unless peer sharing is switched on. That is the whole model, and for most companies it is enough: who reports to whom decides who sees what, and the forecast rolls up the same lines.

On this card the rep in the west region sees her eleven accounts and nothing else. Fine, until the market stops matching the chart. Here is the market problem. The company has decided that its twenty largest accounts, wherever they are, get a dedicated enterprise team. Those accounts are owned by reps in both regions. The enterprise team reports to the director, not to either regional manager. Now two reporting lines need to see the same accounts, and the hierarchy has no line between them. The three fixes from the intro all happen here.

Move the enterprise team under the west manager: now the east accounts are invisible. Make the enterprise lead a peer of both managers: now the forecast double counts. Share the accounts one by one: now someone maintains a list by hand forever. Each fix is a role edit, and each role edit moves what rolls up. The problem is that the market divides by account size and the org chart divides by region. They are two different cuts. Territory management is the second cut. A territory is defined by criteria on the account, in one sentence: accounts above a revenue band; accounts in the west; accounts in the healthcare industry.

Any user assigned to the territory sees the accounts that match, whoever owns them. An account can sit in several territories at once, up to ten; a deal sits in exactly one, which is what keeps the forecast clean. In the mock demo the enterprise territory is defined as accounts rated at the top band on the standard Rating field. The twenty largest accounts match automatically, the enterprise team is assigned to the territory, and both regional reps keep their ownership and their view. Nobody edited a role. Roles decide what rolls up.

Territories decide what reaches across. The reason to do this properly is the forecast. With territories on, the forecast can be built on the territory hierarchy instead of the role hierarchy: the enterprise territory forecasts its own number, each region forecasts its own, and the director's number is the sum without double counting. The three broken forecasts from the intro were all attempts to get this from roles alone. Now the caveat, and it is the reason this is a decision and not an experiment. If you build forecasts on the territory hierarchy and later switch territory management off, those forecasts become inaccessible.

Territories are Enterprise and Ultimate only, so switching off is a real temptation at renewal time. Decide once, test it in the sandbox first, and do not turn it on to see what happens. So here is the question to answer before you touch either tool. Does your market divide the way your org chart does? If every account's right owner is decided by who reports to whom, roles are enough, and adding territories adds overhead and nothing else. If there is a second cut, by size, by industry, by product line, by geography that crosses the reporting lines, that is a territory, and you will know it is one because you can name its criteria in one sentence.

If you cannot name the criteria in one sentence, do not switch it on; the articles behind this video say the same. And one more reason visibility matters now: an agent working in your Zoho CRM inherits exactly these rules, roles and territories both, so whatever you decide here is also what the agent will see. We have a video on that. Roles roll up; territories reach across. Use the org chart for who reports to whom, use territories for how the market divides, and never fix the second with the first.

Answer the one question, name the criteria in a sentence, test it in the sandbox, and decide once, because the forecast you build on territories stays with them. We are CodeStringers, a Zoho authorised consulting partner. The two territory articles and the edition video are linked below, and so is a no-risk discovery, paid only if you proceed.