A multi-tenant LMS runs several client organizations on one platform. Each client gets its own participants, administrators, branding and reports, and no client can see another. Training companies buy it for three reasons. They pay for one platform instead of an LMS per client, run every client’s site from one back end, and see every client’s results in one place.
The word alone won’t tell you what you’re buying. When a vendor pitches your training company “multi-tenant” or “white label multi-tenant,” it could mean separate client environments or one account with its folders renamed. This guide gives you a definition to hold the vendor to, a quick test for whether you need tenants at all, and seven questions that expose a relabeled claim.
Deliver one course to many clients by link, embed or SCORM export – the same material, sent to wherever each client’s participants already take training.
Key Takeaways
NIST’s “multi-tenant model” is how a cloud vendor hosts its customers, not your clients.
Moodle Workplace keeps all tenants’ users in one table and still keeps them apart, so the real risk is the sharing switch.
Vendors sell tenancy under their own word, like a TalentLMS “branch” or Docebo’s “extended enterprise,” and the word alone says nothing about how much separation comes with it.
A client needs a tenant only for its own administrator, its own sign-in or strict separation, while a client with its own LMS needs a SCORM package.
What “Multi-Tenant” Means When a Vendor Says It
A tenant is one client’s walled-off space inside a shared platform. One codebase runs every tenant, and software keeps each tenant’s people and records apart.
The term comes from cloud computing, not from learning management systems. NIST, the US standards body, defines it in Special Publication 800-145, under a characteristic it calls resource pooling. The text reads: “The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand.”
NIST lists resource pooling as one of five essential characteristics of cloud computing. So a cloud vendor that calls its LMS multi-tenant may only be describing how it hosts its own customers. That’s the sense covered in who runs your LMS and where the data sits. It isn’t what a training company pays extra for.
What you pay for is the second sense: tenants inside your own account, one per client, each with its own administrator, participants, branding and reports. Sales pages blur the two because both can be true of the same product. So open with “multi-tenant for whom: your customers, or my clients?” If it’s the first, you’ve learned how they host, not what you’d get.
Do You Need Tenants, or Just Groups?
Tenancy is a per-client need, not a company-wide one. Sort your client list before you sit through a demo, because the sort decides whether this purchase exists at all.
A client needs its own tenant when at least one of these is true:
-
Their own administrator runs their people. Someone at the client adds participants, assigns courses, sets completion rules and pulls reports without calling you. Firmwater, which sells an LMS to training companies, describes exactly this job for customer administrators.
-
They must never see another client. Participant lists, completion reports and certificates stay invisible to your other clients, and that includes exports.
-
They sign in their own way. Their participants log in through the client’s identity provider, on the client’s domain, under the client’s brand.
A client doesn’t need a tenant in three common cases.
They already run an LMS. Some corporate clients only take training inside their own system, so what you owe them is a package it can import, usually a SCORM file. A tenant on your platform just adds a second login. Firmwater sells client sites, and even it answers this case with “host it here, deliver it there.”
Participants come as individuals. Delegates from ten companies who book your open certification course don’t need ten tenants. They need an enrollment, a course and a certificate.
It’s one organization with many parts. A client with five sites that wants a report per site needs groups and roles inside one space, not five tenants. Tenancy is normally sold by the count, so don’t pay for five when groups and roles do the job.
A worked example
Take a six-person training firm with nine client programs. It’s an illustration, not a real firm. Three of its clients run their own LMS and want SCORM packages, four send delegates to open certification courses, and the last two want a branded academy their own HR administrator runs.
Only two of the nine need tenants. Price tenancy for two clients, not nine, and deliver the other seven the way they already take training. The questions later in this guide only have to hold up for those two.
If you run a partner program at a software vendor rather than a training business, swap “client” for “partner tier”: the sort and the questions still work. Partner training platforms compared on how they count users covers the platforms.
Three Ways Vendors Build Tenancy
Vendors keep tenants apart in one of three ways. eLeap Software, an LMS vendor, names all three in an implementation guide written for teams building a platform. Each one changes where you push.
| Build | How clients are kept apart | What it means for your clients’ data |
|---|---|---|
| Shared database, shared schema | Every record carries a tenant ID, and every query filters on it | Cheapest to run. Separation depends on that filter being applied everywhere: screens, reports, exports and the API |
| Shared database, separate schema | Each tenant gets its own set of tables inside one database | Stronger separation, and more maintenance for the vendor |
| Separate database per tenant | Each tenant’s records sit in their own database | The strongest separation and the highest running cost for the vendor |
eLeap describes the first build as one that “uses tenant identifiers to distinguish data within shared tables.” It calls the third “the most isolated multi-tenancy approach.” It also warns that it “increases infrastructure complexity and operational costs.”
That cost order shows up in pricing. Docebo, for one, lists a dedicated database as an Enterprise-tier item. Tempted to build your own instead? The same three choices land on your team, so start with what building your own LMS involves.
None of the three builds is fake. A shared-schema platform can keep clients apart well, and a separate-database platform can still leak through a badly scoped report. The fake version is one account with its groups renamed “tenants.” There, a client administrator is really a group manager who can see beyond their own group.
So the build doesn’t tell you whether a claim is real. It tells you where to test. On a shared schema, test reports, exports and the API. On any build, ask who can override the separation, and get the vendor to name its build in writing.
What Real Isolation Looks Like: Moodle Workplace
Moodle Workplace publishes what a tenant contains, which makes it a useful yardstick. Multi-tenancy is a Workplace feature, sold only through Moodle Certified Partners and Service Providers. It isn’t part of the free, open-source Moodle.
Workplace uses the first of the three builds. “All user information from each tenant is stored in the same database and table,” its documentation says. The application does the separating, and by default it’s thorough:
- “Each tenant has its own users, hierarchies, roles, dynamic rules, theme settings, reports, and learning entities (courses, programs, and certifications).”
- “Users in one tenant cannot see the users in another.”
- “Each user belongs to a single tenant.”
- “Site-wide features are global and apply across tenants,” while “tenant-aware features can be configured for each tenant.”
Then comes the sentence that matters most: “Administrators can choose to enable sharing between tenants, allowing users to see others from different tenants.”
Three lessons carry over to any vendor you’re weighing.
-
A shared database isn’t the risk. Workplace keeps everyone in one table and still keeps clients apart. Judge a platform on what the application enforces, not on where the rows are stored.
-
The tenant-aware list is the spec. Ask your vendor for its own version: which settings, reports and content belong to one tenant, and which apply to everyone. Anything site-wide is something every client shares.
-
The sharing switch is where isolation ends. Find out who can turn it on and whether your client is told.
One wrinkle hits trainers hardest. If each person belongs to one tenant, where does a facilitator who teaches for three of your clients sit? Ask before you import a single account.
Branch, Portal, Organization, Tenant: One Idea Under Six Names
Of the seven platforms below, only Moodle Workplace calls the unit a tenant. The others use their own name, and the name hides how much separation comes with it. Here’s how each describes the unit, in its own words. What a plan meters and charges for that unit is a separate question, answered in what each white label layer costs.
| Platform | Their word | What the vendor says one unit includes |
|---|---|---|
| TalentLMS | Branch | An independent training portal for a different team, department or program |
| CYPHER Learning | Portal | Its own domain or subdomain, design, settings, participants, admins and roles |
| Docebo | Extended enterprise | A separate environment per audience with “different administrative rights and distinct branding elements”, and, in its partner training FAQ, “completely separate authentication processes for different user groups” |
| LearnUpon | Portal | Custom URLs with references to LearnUpon removed |
| Intellum | Organizations | “Its own branded subdomain, permissions, and access” for each audience |
| Thought Industries | Panorama | “Custom co-branded, multi-tenant portals” |
| Moodle Workplace | Tenant | Its own users, roles, theme, reports and courses |
Two things follow from that table.
“Portal” can mean a tenant or a theme. CYPHER Learning’s portal comes with its own admins and roles. On another platform, the same word can mean a branded login page in front of one shared account. Ask for the vendor’s list of what one unit includes, and set it beside Moodle Workplace’s.
Authentication separates a tenant from a skin. Asked whether employees and partners can have different single sign-on setups, Docebo’s FAQ answers with separate sign-in processes per user group, and that’s the test that matters. Can each client’s participants log in through the client’s own identity provider without you running it? A logo swap on a shared login page fails.
In plan names and documentation, look for “extended enterprise” as well as “multi-tenant.” It’s the label vendors use for training people outside your company. Extended enterprise platforms compared on what they count covers that side of the market.
Seven Questions That Test a Multi-Tenant LMS Claim
Run the first three live in the demo. Send the other four in writing, and ask for the answers on the order form or in the security documentation. Each question has an answer that sounds right and an answer that should stop the deal.
-
“Show me two live tenants in this account, now.” Log in as one tenant’s administrator and search for a participant you know sits in the other tenant. A real platform returns nothing. The warning sign is a slide, a mockup or “we’d configure that during implementation.”
-
“What can a tenant administrator do without calling you?” Ask them to click through what an LMS administrator does day to day: add a participant, assign a course, change the branding, run a report, issue a certificate. If the answer stops at branding and a user list, you’re looking at a group with a logo.
-
“Can each client’s participants sign in through the client’s own identity provider?” A real answer shows sign-in configured per tenant. One login page with a swapped logo isn’t separation. Ask what single sign-on costs while you’re there.
-
“Which of the three builds do you run, and what separates my clients if another of your customers has a security incident?” A real answer names the build and the controls. “It’s enterprise-grade” names neither. If IT is running a full vendor security review alongside yours, this is the question to hand them first.
-
“Who can switch on sharing between tenants, and is my client told?” A real answer names a role and a record of the change. If nobody on the call knows whether the switch exists, assume it does.
-
“Can a report, an export or an API key ever return more than one tenant’s records?” Ask about each one separately. A report that rolls up across tenants is useful to you and dangerous in a client administrator’s hands.
-
“When a client leaves me, can you export that one tenant’s participants, completions and certificates on their own?” Clients come and go in a training business. A platform that can only export everything at once turns a contract ending into a data-handling problem.
A vendor that passes all seven is selling separate client environments. One that stalls on the first is selling groups. Any answer they won’t put in writing, from the build to the single-client export, belongs on your list of questions to settle before you sign.
Where Mini Course Generator Fits
Mini Course Generator is our product, and it isn’t a multi-tenant LMS. There are no sub-accounts, per-client instances or reseller tier on any of our plans. A client that needs its own administrator running its own academy needs a platform that passes the seven questions above.
MCG fits the clients who don’t need a tenant. For a client that runs its own LMS, courses export as SCORM or PDF. For delegates who come as individuals, a course can be limited to specific learners or sit behind a Password Wall.
Some clients just want to see their own name. The Mini Course Generator badge comes off on every paid plan, and invitation and verification emails can go out from your own domain. You get one custom domain on Plus, three on Pro, Launch and Growth, and unlimited on Scale and Custom.
The Scale plan also adds account-based reporting for your customers’ admins. That’s visibility, not a separately administered space, so it doesn’t pass the tenancy test.
Ask for Two Live Tenants Before You Ask for a Price
Sort your client list first, and count the clients that need their own administrator, their own sign-in or strict separation from everyone else.
Zero? Stop shopping for tenancy and deliver by export, enrollment or groups. One or more? Open the next demo with question 1, and don’t talk price until you’ve seen two live tenants and heard a straight answer about the sharing switch.
Train clients and partners outside your company – build a course once and deliver it to each audience the way they already take training.
Frequently Asked Questions
What’s the difference between a multi-tenant and a single-tenant LMS?
A single-tenant LMS gives one customer its own instance, usually its own database or servers. A multi-tenant LMS runs many customers on shared infrastructure and keeps them apart with software. For a training company, the more useful question is whether you get tenants of your own to hand to clients. That’s a separate feature from how the vendor hosts you.
Is a white label LMS the same as a multi-tenant LMS?
No. White label is whose brand participants see. Multi-tenant is how many separately administered spaces you get. You can have one without the other: TalentLMS removes its branding on every paid plan, and its entry plan includes one branch.
Does a multi-tenant LMS cost more than a regular account?
Often, because tenancy is sold by the count. Firmwater, which sells client sites to training companies, starts at $625 a month for five client sites and 100 active learners, on a one-year minimum. That’s a $7,500 commitment. Vendors meter that count in their own way, so price the count you’ll need once your client list grows, not the one you need today.
Is extended enterprise the same as multi-tenant?
Not quite. Extended enterprise is the vendor label for training people outside your company, and one account can hold several. Docebo’s FAQ describes “an extended enterprise for franchisees, one for channel partners, one for resellers, one for customer training.” Whether each one is a real tenant comes down to the same tests: its own administrator, its own sign-in and no view into the others.
Do I need a multi-tenant LMS to sell training to other companies?
Not always. If your clients import courses into their own LMS, you need a clean SCORM export. If each client wants an academy its own team runs, you need tenancy, and the seven questions above decide whether a vendor has it.
Sources
Vendor documentation, pricing and product pages read September 2026.
- NIST SP 800-145, The NIST Definition of Cloud Computing, Peter Mell and Timothy Grance, September 2011
- Moodle Docs, Multi-tenancy (Moodle Workplace)
- eLeap Software, Multi-Tenancy in LMS: Complete Implementation Guide
- Firmwater, multi-tenant LMS page and pricing page
- TalentLMS pricing page
- CYPHER Learning pricing and platform pages
- Docebo pricing page, extended enterprise product page and FAQ, and partner training page FAQ
- LearnUpon pricing page and portals feature page
- Intellum platform pages
- Thought Industries Panorama pages
- Mini Course Generator pricing page
