Multi-tenant LMS: a real boundary per client, not a naming convention
Multi-tenant means each customer gets a workspace that behaves like their own installation — their domain, their branding, their users, their data — while one shared platform runs underneath. It is the difference between a training business having an account and a training business having a product.
What multi-tenancy actually buys you
The word is used for two different things, and buyers get caught out by the gap.
Multi-tenant as the vendor's architecture
Every SaaS product is multi-tenant in this sense: one deployment serves many customers, which is why it costs what it costs and why you get upgrades without a migration project. This tells you nothing about what your learners see.
Multi-tenant as something you can use
The useful sense: you can create separate spaces inside your own account. A training company delivering to twelve corporate clients does not want twelve rosters in one list, twelve clients' managers able to see each other's completion rates, or twelve separate subscriptions to administer. It wants twelve tenants it controls.
That is what sub-organisations are here: a separate roster, separate cohorts and a separate reporting roll-up per client company, inside one workspace with one catalogue and one bill. Each client's administrator sees their own people and their own numbers, and nothing else.
Where the tenant boundary sits
| Layer | Separated per tenant | Shared |
|---|---|---|
| Hostname | Yes — each workspace has its own, and can use a domain you own | — |
| Branding | Logo, colours, typeface, favicon, learner email sender | — |
| Users and enrolments | Yes | — |
| Cohorts, schedules, attendance | Yes | — |
| Reporting | Rolls up per client company | You see the whole picture |
| Course catalogue | Assigned per tenant | Authored once by you |
| Billing | — | One relationship with us |
Authoring once and assigning per tenant is the point. A compliance course you update in January should reach all twelve clients in January, without twelve uploads.
Why this shape suits a training business
A platform built for a single company's internal L&D assumes one organisation, one brand and one set of managers. Bend it to serve a business whose customers are other businesses and you end up with naming conventions instead of boundaries — client names prefixed onto group titles, spreadsheets to work out who may see what, and an access mistake waiting to happen.
Tenancy handles it structurally instead. A client administrator cannot see another client because there is no view in which the two appear together, not because someone remembered to filter.
Running it day to day
- A new client is a new sub-organisation, not a new subscription.
- Courses are assigned to it from your existing catalogue.
- Their people are invited, or bulk-imported, into their own roster.
- Cohorts and live sessions are scheduled per client, with their own attendance capture.
- Certificates issue under your brand — or theirs, if that is what you sell.
- Reporting rolls up per client, and across all of them for you.
The SaaS part
Nothing is self-hosted and there is no server for you to patch. A workspace is live in about a minute, upgrades arrive without a migration, and the custom domain gets its certificate automatically when you point a CNAME at us. If you need a dedicated deployment for procurement reasons, that is what the Enterprise tier is for — but it is the exception, not the default.
No card. The workspace is live in about a minute, on its own address, and you can point your own domain at it the same day.
Questions we get asked
What is a multi-tenant LMS?
A learning platform where each customer gets a workspace that behaves like their own installation — their own hostname, branding, users and data — while one shared platform runs underneath. The useful version also lets you create separate tenants inside your own account, one per client company.
How is that different from groups or user categories?
Groups filter a shared list; tenants separate it. With sub-organisations there is no view in which two client companies appear together, so a client administrator cannot see another client's people even by accident.
Can each client company have its own administrator?
Yes. Each sub-organisation has its own roster, cohorts and reporting roll-up, and its administrators see only that client.
Do I have to upload a course once per client?
No. You author once and assign the course to whichever tenants should have it, so an update in January reaches every client in January.
Is it self-hosted or SaaS?
SaaS — there is no server for you to patch, and a workspace is live in about a minute. A dedicated deployment is available on the Enterprise tier for buyers whose procurement requires it.