Teams and locations

Administration → Org Structure.

Locations

A hierarchy. A location can contain other locations:

India
├── West
│   ├── Mumbai — Andheri
│   └── Pune — Baner
└── South
    ├── Bengaluru — Indiranagar
    └── Chennai — Adyar

Locations do three things:

1. Scope visibility — a manager scoped to location sees their branch and everything under it
2. Route leads — territory rules assign by location
3. Roll up reporting — West's numbers are the sum of Mumbai and Pune, automatically

Depth is unlimited, but past three levels the reporting becomes hard to read. Country → region → branch covers almost every organisation.

Teams

A team is a group of people with a manager. Unlike locations, teams are flat — a team does not contain other teams.

Teams are what the team data scope resolves against. A team lead scoped to team sees the records owned by everyone in their team, and their own.

A person can belong to more than one team. Their team scope then covers all of them.

Choosing between them

They answer different questions:

• Location — *where* someone works. Usually stable, usually maps to a physical office.
• Team — *who* they work with. Changes more often, may cut across locations.

A common structure: locations for branches, teams for desks within a branch. A "Enterprise Desk" team might span Mumbai and Bengaluru while both remain distinct locations.

Effect on reporting

Analytics → Team Performance groups by team. Location-scoped reports group by location. Both are available on the same data — you are not choosing one at the expense of the other.

Reassigning after a reorganisation

Changing someone's team or location takes effect immediately for visibility, but historical records keep their original attribution. A lead owned by someone who has since moved branch still counts to the branch that worked it.

This is deliberate. Retrospectively rewriting which branch earned last quarter's revenue would make every report you have already published wrong.