Some businesses are one company. Others are a holding group, a franchise network, or an agency running several brands that should not see each other’s clients. Multi-organization support is the difference between modelling that reality and papering over it with naming conventions and trust.
When you actually need it
- Holding groups where subsidiaries have separate P&Ls and separate sales teams
- Agency groups running distinct brands, sometimes for competing clients
- Franchise or partner networks where each operator owns their own pipeline
- Multi-entity structures in India with separate GST registrations and separate books
If none of these describe you, do not enable boundaries you will spend the next year working around. Complexity you do not need is a permanent tax.
Boundaries, drawn
The three design questions
- Which objects are global? Users and product data usually; customer records almost never.
- Can anyone see across? Group leadership normally needs consolidated reporting—decide whether that means access to records or only to aggregates.
- What happens to a shared customer? When two units sell to the same company, do they see one account or two? There is no universally right answer, but there is a wrong one: leaving it undecided.
Switching context beats switching logins
People who work across two units should not maintain two passwords. In Vertex CRM, users assigned to multiple organizations switch context from the header, with permissions evaluated per organization—so an account manager can be an administrator in one unit and a read-only contributor in another. Fewer credentials also means cleaner audit trails and fewer shared-password shortcuts.
Reporting across the boundary
Group leadership wants one number; the boundary exists to stop record-level leakage. Those goals are compatible if you separate them explicitly: aggregate reporting at the group level, record access only where someone has an assignment. Write down which roles get which, and review it when the structure changes.
Governance that stays honest
Boundaries decay quietly. A quarterly access review—who has multi-organization assignments, and why—is a fifteen-minute task that prevents the slow drift toward everyone having access to everything. Pair it with the audit trail so the review has evidence behind it.
Related: team collaboration and roles, CRM for agencies, and security and compliance.
Frequently asked questions
- When do you need multi-org?
- Holdings, franchises, partner programs, or agencies running distinct workspaces.
- Does switching org require new login?
- Users with multiple assignments can switch context without separate passwords when configured.