CRM Basics
The organisation view and the tribe view
Why the same CRM screens exist twice, what each one shows, and which one to use for which job.
Last updated September 2, 2026
The CRM screens appear in two places. It is the same data — what changes is how much of it you are looking at. A tribe is one location, branch or business unit inside your organisation.
| View | Shows | Use it for |
|---|---|---|
| Organisation → CRM | Every tribe at once | Head office: comparing tribes, network-wide reporting, and the settings every tribe shares. |
| A tribe → CRM | That tribe only | Everyday selling. This is where reps live. |
What belongs to a tribe
- Contacts belong to one tribe. That is what lets a tribe report on its own customers without the rest of the network in the numbers.
- Companies are per tribe. Two tribes dealing with the same national chain each hold their own record of it, with their own contacts and their own history.
- Opportunities, tasks and call lists follow the tribe of the record they are on.
What is shared across the whole organisation
Everything in CRM Settings: lifecycle stages, opportunity stages and types, lead sources, statuses, custom fields, task priorities, event types. They are defined once and every tribe uses them.
THAT IS THE POINT
Shared settings are what make network reporting possible. If every tribe invented its own stage names, no report could ever add them up.
Which one am I in?
The breadcrumb at the top tells you: an organisation screen shows your organisation name, a tribe screen shows the tribe name after it. The menu is the other giveaway — Merge Contacts and Team Members only appear inside a tribe.
A NUMBER THAT LOOKS WRONG IS USUALLY THE WRONG VIEW
A pipeline figure that seems far too big, or a contact count nobody recognises, is nearly always the organisation view being read as though it were one tribe. Check the breadcrumb before you go looking for a data problem.