Extended enterprise LMS: multitenancy in Totara for associations and training companies

Most learning platforms were designed for one organisation training its own staff. Associations and training companies rarely work that way. You train your members and their employers, your chapters, your certified partners, your corporate clients, and often your own team as well, and each of those audiences expects to see its own programme rather than everyone else's.

An extended enterprise LMS is built for that shape of organisation. Totara LMS handles it through multitenancy: one platform, divided into separate spaces for separate audiences, each with its own users, branding, administrators and reporting, all managed from a single site.

This page explains how Totara multitenancy works, who it suits, where Totara's licensing draws the line, and how it compares with Moodle.

What multitenancy means in a learning platform

Think of an office building. The building has one set of foundations, one lift system and one maintenance contract. Each floor is leased to a different tenant, with its own reception, its own signage and its own staff, and nobody on the fourth floor walks into the offices on the ninth.

A multi-tenant LMS works the same way. There is one installation, one upgrade path and one set of courses maintained centrally. Inside it, each tenant is a separate space for a defined group of users, who log in to their own branded experience and see only what is meant for them.

The alternative is a separate site for every audience. That works at two or three sites. At twenty, you are maintaining twenty upgrades, twenty copies of the same course, and twenty sets of reports that someone has to stitch together by hand.

What each tenant gets in Totara

Multitenancy is part of Totara Learn itself and extends to Totara Perform. Totara's version 20 functionality overview lists the following under extended enterprise:

• Tenant administrators, so a chapter lead or a client's training coordinator can manage their own people without site-wide access
• Tenant-specific content, dashboards and reporting
• Tenant themes, images and login pages, so each audience sees its own brand
• Tenant bulk upload for loading users
• Report content filters and support for multiple authentication methods
• In Totara Perform, tenant-specific performance activities

Users are associated with a tenant, and role permissions respect that association. A tenant administrator's authority stops at the edge of their tenant.

Two levels of separation

Totara gives you a choice about how separate tenants really are.

By default, tenants can still see site-level content and users. That suits organisations where some learning is shared by everyone, such as an association's code of conduct course that every chapter and every member employer should take.

Tenant isolation is the stricter option. With isolation enabled, the content and users in each tenant are fully separated from other tenants, and tenant members can only see and interact with courses, programs and people inside their own tenant. That suits a training company whose corporate clients must never see each other's staff, completions or even existence.

The right setting depends on your audiences, and it is one of the first architecture decisions in a multi-tenant Totara build.

Who multitenancy suits

Associations

Associations are usually several organisations in one. A regional or provincial chapter structure maps naturally to tenants, with chapter administrators managing their own members and reporting. Member employers who send staff through your accredited programmes can each have a tenant, so their coordinators can enrol people and track completion without seeing any other employer's workforce. Courses, programs and certifications stay centrally owned by the association, which is where accreditation and quality control need them to be.

Training companies

A training company that creates its own curriculum and delivers it to client organisations is one of the use cases Totara explicitly recognises. Each client gets a branded tenant, its own coordinators with basic user administration, and completion reporting for its own people. Your team builds and maintains the courses once, centrally, and every client sees the current version.

Extended enterprise programmes

An organisation training its own staff alongside an external audience, such as a dealer network, resellers, franchisees or customers, can run both from one site. Internal staff and each external group sit in separate tenants, while shared product and compliance training is created centrally and assigned where it applies.

Healthcare networks and parent organisations

Separate business units under one parent, such as partner hospitals in a health alliance or regional divisions of a national employer, can share a common compliance curriculum while keeping local administration and reporting local.

Where Totara's licensing draws the line

This section matters most to training companies, and most multitenancy pages leave it out.

Totara publishes an acceptable use policy for multitenancy. Its stated principle is that multitenancy exists to serve multiple audiences efficiently, not to reduce the number of subscriptions an arrangement should carry.

Totara describes these uses as acceptable:

• Parent and child organisations, such as business units of one company in different regions
• Extended enterprise, where one organisation serves its staff and an external audience, with courses created centrally
• Franchise groups
• Training providers that create all the courses and distribute them to external organisations, whose tenants consume that content, perform basic user administration and report on completions

Totara describes these uses as not acceptable:

• Hosting one Totara site under one subscription and selling tenant space to different organisations
• Unrelated organisations sharing one site where separate subscriptions should be in place

In practical terms: if you author the training and your clients take it, multitenancy is designed for you. If your clients want their own LMS to build and run their own courses in, each of them needs their own Totara subscription, and a good partner will scope it that way from the start rather than discover it at renewal.

Totara compared with Moodle for multi-tenant programmes

Moodle is an excellent platform, and Lambda Learning hosts and supports it. For multi-tenant programmes specifically, the editions differ.

Moodle LMS can be configured to separate content by audience using course categories, cohorts and category-level permissions. What it does not do by design is separate users, so every learner still exists in one shared population, and site-wide reports see all of them. For a handful of internal departments that is often fine. For client organisations who must not see each other, it is a workaround rather than an architecture.

Moodle Workplace closes that gap with full multitenancy. Lambda Learning does not offer Moodle Workplace, so if Workplace is your preferred route, a Moodle Certified Partner is the right conversation, and we would rather tell you that here than on a sales call.

If you are weighing the two platforms more broadly, our comparison of Moodle and Totara covers licensing, compliance and customisation beyond multitenancy.

Decisions to make before you build

A multi-tenant site is easy to start and expensive to restructure. These are the decisions worth settling in the first weeks of an implementation.

Tenant model. Map your real audiences first: chapters, member employers, clients, partners, internal staff. Decide which are tenants and which are better handled as audiences or organisational hierarchies inside a tenant. Not every grouping needs to be a tenant.

Isolation. Decide whether any tenant must be fully invisible to others. Switching isolation on after launch is possible, but it changes what learners and administrators can see, so it is better decided up front.

Shared versus tenant content. Decide which courses, programs and certifications are site-wide and which belong to a single tenant. For training providers and extended enterprise programmes, Totara's policy expects course creation to stay central.

Audience rules. Dynamic audiences built with broad rules can pull in users from every tenant. Totara provides a tenant membership rule for exactly this reason, and it should be part of every audience that is meant to stay inside one tenant.

Administration. Decide what a tenant administrator can do: enrol users, run reports, upload users in bulk. Keep it to what each audience actually needs.

Reporting. Tenant administrators see their own tenant. Your central team needs the cross-tenant view, and it is worth designing both at the same time.

Reporting across tenants

Totara's report builder produces tenant-specific reports for tenant administrators and site-wide reports for your central team, which covers most operational questions: who is enrolled, who has completed, whose certification is about to lapse.

Where the questions reach beyond the platform, such as revenue per client, renewal risk by member employer, or learning data joined with CRM or membership records, Lambda Learning adds Zoola Analytics on top of Totara.

When multitenancy is not the right answer

• Your clients want to author and manage their own courses independently. That is a separate Totara site and subscription per client, not a tenant.
• The organisations you would group together are unrelated to each other and to you. Totara's policy does not permit that arrangement under one subscription.
• You have two or three audiences with light separation needs. Audiences and organisational hierarchies may do the job without the added architecture.
• Each client needs a different version of the platform, different plugins or deep per-client customisation. Tenants share one installation, so they share its code and upgrade schedule.

What Lambda Learning adds

Totara is delivered through partners, and with multitenancy the partner's architecture decisions matter as much as the platform. Lambda Learning has been implementing learning platforms since 2002 for associations, healthcare organisations, compliance teams and training companies.

• Tenant architecture design, including isolation, audience rules and administrator permissions
• Implementation, configuration and custom development against your programme
• Managed hosting and ongoing support
• Zoola Analytics for reporting across tenants and beyond the LMS
• Lambda Store for selling courses, memberships and credentials to the audiences you serve

On hosting, we do not own data centres. Lambda Learning runs Totara on Amazon Web Services, currently in four regions: Canada (ca-central-1), the United States (us-east-1 and us-west-2) and Europe (eu-west-1). A Canadian customer's data is stored, loaded, updated and deleted on services wholly within the Canadian region.

Frequently asked questions

What is an extended enterprise LMS? An extended enterprise LMS trains people outside your own workforce, such as members, customers, partners, resellers or client organisations, usually alongside internal staff. It needs to keep those audiences separate while letting you manage training centrally, which is what multitenancy provides.

Does Totara support multitenancy? Yes. Multitenancy is part of Totara Learn and extends to Totara Perform. Each tenant can have its own administrators, branding, login page, content, dashboards and reporting, with an optional isolation mode that fully separates tenants from each other.

Does Moodle support multitenancy? Not in Moodle LMS, the standard open source edition. Moodle Workplace, a separate commercial edition sold through Moodle Certified Partners, includes full multitenancy. Moodle LMS can approximate separation with course categories and cohorts, but it does not separate users by design.

Can a training company use Totara multitenancy to serve clients? Yes, when the training company creates the courses and client organisations take them. Totara's acceptable use policy recognises this model. Selling tenant space so that unrelated organisations can run their own LMS under one subscription is not permitted.

Can each tenant have its own branding? Yes. Tenants can have their own theme, images and login page, so each audience sees its own brand.

Can tenant administrators see other tenants? No. A tenant administrator's permissions are limited to their own tenant. Your central site administrators can see across all tenants.

Is multitenancy more secure than separate sites? It is a different trade-off rather than a stronger or weaker one. Separate sites isolate everything, including code and database, at the cost of maintaining each one. Multitenancy separates users and content within one installation, with isolation mode for the strictest separation, and gives you one platform to secure, upgrade and audit.

Where is a multi-tenant Totara site hosted? Lambda Learning hosts Totara on Amazon Web Services. Canadian customers are hosted in the Canadian region, with data stored, loaded, updated and deleted wholly within it.

Planning a multi-tenant programme? Talk to a Totara partner who will tell you where it fits.

Tell us about your audiences and we will sketch how they map to tenants. If multitenancy, or Totara, is not the right fit for your programme, we will say so.

Book a demo: https://www.lambdalearn.io/schedule-a-meeting-lambda-suite

Talk to a specialist: https://www.lambdalearn.io/schedule-a-meeting-lambda-suite

Totara, Totara Learn and Totara Perform are trademarks of Totara Learning Solutions Ltd. Lambda Learning Inc. is a Totara Platinum Partner. Moodle and Moodle Workplace are trademarks of Moodle Pty Ltd.