Capabilities
White label LMS versus client portals: what is actually separate?
White label means the platform removes its own brand from your school: your logo, your domain, your emails. A client portal means each corporate client gets a separated space: its own catalog view, user pool, admin rights and reporting. Most platforms document the first and stay vague on the second. The matrix below shows exactly what is published, per platform and per dimension.
Six things that can be separate, or not
When an agency or training company says white label, it usually means one of six different needs. Name the one you actually have before any demo:
- Branding: whose logo and colors the learner sees.
- Domain: whether each client can get its own web address.
- Catalog: whether each client sees only its own courses.
- Users: whether client A's learners exist in client B's space.
- Admins: whether a client manager can run their people without touching yours.
- Data: whether progress and reporting are separated per client.
A logo swap solves the first one. Only real separation solves the last three.
The separation matrix
Filter by the dimension you need and the platforms you are considering. Every cell reflects published commitments at our last registry check, nothing more.
Filter the separation matrix
| What you need separate | Thinkific | LearnWorlds | Teachable | Podia | LearnDash |
|---|---|---|---|---|---|
| Custom branding per client | Partial, shared school Branding removal from Grow applies to one school, one brand. Per-client branding is a Plus conversation. | Partial, shared school Full white label from Learning Center covers your school; client groups share that brand unless you go Corporate. | Partial, shared school Branding removal on Growth; no per-client branding as published. | Not published, ask in a demo Branding terms are not itemized on the pricing page. | By construction, separate installs Each WordPress install is fully the client's brand; one license covers one site. |
| Custom domain per client | Partial, shared school One custom domain per school. Per-client domains are not published below Plus. | Partial, shared school One school domain; per-group domains are not published. | Partial, shared school One custom domain from Builder. | Partial, shared school One custom domain per account. | By construction, separate installs One install per domain, so per-client domains are structural. |
| Separate catalog per client | Partial, shared school Group selling from Grow shares one catalog; you scope access, not the catalog itself. | Partial, shared school Client groups (1 on Pro Trainer, up to 10 on Learning Center) receive assigned courses from one catalog. | Not offered as published No published client portal or group concept. | Not offered as published Spaces are communities, not client portals. | By construction, separate installs Separate installs mean separate catalogs; within one install, groups share the catalog. |
| Separate user pool per client | Partial, shared school Groups segment one shared student base inside the school. | Partial, shared school Groups are segments of one user base, not separate schools. | Not offered as published One student base per school. | Not offered as published One customer base per account. | By construction, separate installs Separate installs keep user pools apart; within one install, groups share the user table. |
| Client admin rights | Not published, ask in a demo Delegated client-admin rights below Plus are not documented publicly. | Not published, ask in a demo Per-group admin delegation is not itemized publicly. | Not published, ask in a demo Only admin seat counts are published. | Not offered as published Assistants are staff seats, not client admins. | Partial, shared school Group leader role exists within one install; rights depend on tier and setup. |
| Separated client data | Not published, ask in a demo No public commitment on per-client data separation; confirm the multi-account scenario in a demo. | Not published, ask in a demo No public isolation commitment; verify cross-group access with test accounts in a demo. | Not published, ask in a demo Not documented. | Not published, ask in a demo Not documented. | By construction, separate installs Separate installs mean separate databases; one shared install does not separate data. |
How to read partial and not published
Partial, shared school means the capability exists inside one shared environment: LearnWorlds client groups and Thinkific group selling both segment a single school. That is enough to sell seats to several companies. It is not enough if a client demands that their people and data never share an environment with anyone else.
Not published, ask in a demo is not a no. It means the vendor makes no public commitment, so the answer depends on your contract. We do not use words like isolation or multi-tenant as if they were verified results: proving real separation requires a test with accounts in two client groups trying to reach each other's data. Ask for exactly that scenario in the demo, with fictional accounts, and get the answer in writing. The manager side of that test, who assigns seats and who sees which report, is walked through in client manager seat assignment to admin reporting.
If every dimension must be hard-separated, the honest options change: separate WordPress installs with LearnDash licenses per client, or an enterprise conversation with Thinkific Plus or LearnWorlds Corporate.
What this costs
Branding removal starts at Thinkific Grow ($164 per month on annual billing) and LearnWorlds Learning Center ($249 per month on annual billing). Client groups start earlier at LearnWorlds Pro Trainer ($79 per month, one group). Fully separated client spaces are quote territory everywhere in SaaS, or one LearnDash license plus hosting per client site. Put your own numbers into the cost calculator to see the yearly totals.
Frequently asked questions
Is white label the same as multi-tenant?
Which platform has the cheapest real client portals?
What should I actually test in a demo?
Do I need a separate domain per client?
Keep deciding
Best LMS for a training company selling to businesses
Selling training seats to companies? A grid that separates seats, client autonomy, per-client reporting and data separation across the main platforms.
Selling training seats to companies: the buyer-to-learner workflow
The buyer-to-learner path for B2B seat sales, with named roles and the three things vendors blur: purchase orders, payment, and seat allocation.
From seat assignment to reporting: the client manager's side of a B2B deal
After a B2B seat sale: who assigns seats, which client role sees progress without full admin access, and what five LMS platforms document.
SSO and client admin access: a procurement checklist
SSO, provisioning and delegated rights are three different things vendors blur. A procurement questionnaire and the demo scenario to demand before you sign.
Course platform pricing calculator: Thinkific vs LearnWorlds vs Teachable, Podia and LearnDash
Selling courses? Compare the yearly cost of Thinkific, LearnWorlds, Teachable, Podia and LearnDash from your sales, students, admin seats and transaction fees.