A tribe is one location, branch or business unit inside your organisation. A store, a clinic, a franchise, a sales office, a territory — whatever the unit is that has its own address, its own phone number and its own customers.
Why that word
Because no ordinary word fitted. "Store" is wrong for an office, "branch" is wrong for a franchise, "location" is wrong for a territory with no premises. Tribe is deliberately odd so that it means one thing everywhere in the product.
What belongs to a tribe
| Belongs to the tribe | Belongs to the organisation |
|---|---|
| Its address, phone and opening hours | The brand, and what tribes are allowed to change |
| Its own customers and enquiries | Marketing campaigns and automations, pushed down to tribes |
| Its team members and administrators | Roles and permissions |
| Its page on your website | The website itself |
| Its sales, calls and reviews | Reporting across the whole network |
One tribe, one customer
Each person in your database belongs to a single tribe — the location that deals with them. That is what makes it possible to give a tribe its own leads, report on its own performance, and let it market to its own customers without seeing anybody else's.
The two views of everything
Most modules exist twice: an organisation view covering the whole network, and a tribe view covering a single tribe. The screens look similar on purpose. Which one you are on is shown at the top, and it decides what you can see and change.
Where tribes are managed
From your organisation, open Tribes. The menu lists List All plus one entry per tribe type, then Tribe Status Summary, Tribe Groups, and the settings screens for types, regions and field permissions.