Organisations with branches, regions or member bodies often face the same choice: give every unit its own system, or run one shared platform. A multi-tenant platform is the second approach, done carefully.
What “multi-tenant” means
In a multi-tenant system, one application and one codebase serve many separate units, called tenants. Each tenant sees and manages its own information, while the organisation benefits from shared infrastructure, shared improvements and consistent standards.
Why organisations choose it
- One system to maintain: fixes and new features reach every unit at once.
- Consistency: shared templates, terminology and processes across the organisation.
- Oversight: central administrators can see across units where they are authorised to.
- Lower cost per unit: hosting and support are shared rather than duplicated.
The hard part: separation
The key engineering question is how strictly tenants are kept apart. Common approaches include:
- Shared database with a tenant identifier on every record. Efficient, but every query must filter correctly.
- Separate schema per tenant within one database. Stronger separation with more management overhead.
- Separate database per tenant. The strongest isolation, usually reserved for strict regulatory or contractual needs.
Whatever the approach, separation must be enforced consistently, tested, and never left to individual screens to remember.
Permissions across levels
Organisations rarely have only one level. A national office, provincial structures and local branches may each need different rights. Good role design answers questions such as: who can see what, who can publish, and who can approve changes on behalf of whom. Role-aware access should be designed early, because retrofitting it is difficult.
Shared versus local configuration
Decide which parts of the system are fixed centrally and which each unit may configure. Branding, content and contact details are often local; data structures, security rules and core workflows are usually central.
When it is not the right fit
If units operate in completely different ways, have no shared data, or require full independence, separate systems may be simpler. Multi-tenancy pays off when units share most of their processes and benefit from working on one foundation.
A well-designed multi-tenant platform gives each unit independence where it matters and consistency where it counts.
