28 Apr What Is Totara Multi-Tenancy and Why Does It Matter for Training Organisations?
Totara multi-tenancy is the ability to run multiple separate, isolated organisational environments (tenants) within a single Totara installation. Each tenant can have its own branded interface, its own user base, its own catalogue of courses and learning paths, its own administrative team, and its own reporting environment. From the perspective of a learner inside Tenant A, they are using a platform built for their organisation. They cannot see Tenant B’s content, users, or data. The environments are fully separated.
This is architecturally different from creating user groups or categories within a shared LMS environment. In a grouped setup, separation is enforced by permissions and filters – it can be configured to work, but the underlying data is shared, and the risk of bleed between groups increases with platform complexity. In a genuinely multi-tenant architecture, the separation is structural. Tenant A’s data does not exist in Tenant B’s environment because the platform does not allow it to.
Multi-tenancy is a native capability in Totara Learn, not a workaround or add-on. Totara was built from the outset to support extended enterprise delivery, the model where one organisation provides learning to a network of other organisations, and the multi-tenancy architecture reflects that design intent.
The three types of organisation that truly need a Totara multi-tenacy LMS
Multi-tenancy solves different problems for different types of organisation, but the underlying requirement is the same: multiple separate groups of users, each needing their own environment, all managed from a single platform.
Commercial training providers serving multiple corporate clients
A training provider selling CPD programmes, compliance training, or professional development courses to corporate clients needs each client to have a separate environment. The client’s employees should log into a branded platform that feels like it belongs to their employer. Their completion data should be reportable to their L&D manager without any cross-contamination from other clients’ data. Their administrator should be able to manage their own users without access to any other client’s environment.
Without multi-tenancy, serving ten clients means either running ten separate platform instances, which means ten times the hosting cost, ten separate update cycles, ten separate support arrangements, etc. Or, managing them in a single shared environment with the compliance and governance risks that this model entails. Multi-tenancy removes both constraints. One installation, one maintenance overhead, and as many client environments as the business needs.
Large organisations with multiple departments, offices, or subsidiaries
Multi-tenancy is not only a model for external training delivery. A large employer with distinct operating divisions, regional offices, or subsidiary companies may need each unit to have its own learning environment, each with its own content, its own administrators, its own reporting, while the central L&D or HR function retains oversight across all of them from a single platform view.
This is the internal extended enterprise model. The platform serves the whole organisation from one installation, but each unit operates with sufficient autonomy that it does not need to interact with or be affected by what other units are doing on the same platform.
Membership organisations and professional bodies
A professional membership body delivering CPD to member organisations faces a similar structural requirement. Each member organisation may need its own environment, its own branded access, and its own reporting. But the central body needs to manage content, track completion across the membership, and maintain a consistent platform with one set of hosting and maintenance costs.
What Totara multi-tenancy does not do on its own
Multi-tenancy is the essential architecture for organisations in the situations described above. What it does not do, on its own, is handle the commercial transaction between the training provider and the client organisation.
For an internal L&D deployment, this is not a concern. The platform delivers training; payment does not enter the picture. But for a commercial training provider selling courses or licences to corporate clients, the platform needs to do more than deliver learning in separate environments. It needs to process purchases, generate invoices, track licence allocations, and manage renewals – all for each client independently.
Without a dedicated eCommerce layer, this is managed manually or through a separate payment gateway system. Unfortunately, this often results in the training provider having to issue invoices outside the platform, tracking licence usage in a spreadsheet, and reconciling completion data with billing records at the end of each month. That process works at small scale. It does not work when the client base grows to the point where the administrative overhead of managing it manually becomes the operational constraint on the business.
How Accipio One Shop extends Totara's multiy-tenancy capabilities for commercial training providers
AccipioOne Shop is a plugin built natively for Totara Learn and Moodle Workplace. It adds a full B2B eCommerce layer within the platform. It is not an external integration that needs to be reconciled against the LMS. It operates within the same platform environment, which means the commercial transaction and the learning delivery are part of the same system.
For a training provider using Totara multi-tenancy to serve multiple corporate clients, AccipioOne Shop adds:
- Invoice-based purchasing: a corporate client can request access and receive a formal invoice, with learner provisioning triggered on confirmation rather than requiring card payment at point of purchase
- Purchase order support: PO references are captured as part of the transaction flow, not added manually after the fact
- Per-tenant licence tracking: each client’s licence allocation is tracked within the platform; their administrator can see remaining licences and assign them to new learners without contacting the training provider’s team
- Automated per-client reporting: because multi-tenancy has already separated each client’s data, completion reports are generated per tenant by design, with no manual filtering
- Renewal automation: notification and provisioning workflows can be configured to trigger at defined points before a contract expiry date
The administrative overhead that typically grows with each new client (PO matching, licence reconciliation, per-client reporting, renewal management) is handled by the platform rather than by the operations team. Adding a new client does not add a proportional administrative burden because the system manages it.
The scale that Accipioo One Shop supports
BeReady, deployed on Totara Learn by Accipio, supports over 200,000 users across 4,000 tenanted organisations from a single platform instance. Each of those 4,000 organisations operates in its own isolated environment — its own branding, its own users, its own administrators – managed from one central installation.
Educare also deployed on Totara Learn, supports over 500,000 users across 6,000 client organisations, with eCommerce and CRM integration built into the platform. The combination of multi-tenancy and commercial transaction capability at that scale demonstrates what the architecture can support when the eCommerce layer is part of the platform rather than a separate system.
Is Totara multi-tenancy the right architecture for your organisation?
The multi-tenant model is the right architecture for any organisation that needs to serve multiple separate groups of users, whether those are external clients, internal divisions, or member organisations, each requiring their own environment, branding, and reporting, from a single platform installation.
It is not the right model for every deployment. A single employer delivering training to a single unified workforce does not need multi-tenancy. The architecture adds configuration complexity that is justified when the requirement exists but unnecessary when it does not.
The question worth asking is straightforward: does your organisation currently serve, or plan to serve, multiple separate groups of users who need to be isolated from each other within the same platform? If the answer is yes, multi-tenancy is the architecture you need. If you also sell training to those groups directly – invoicing clients, managing licences, handling renewals – Accipio One Shop is the layer that makes this commercially viable.
For organisations evaluating whether Totara’s multi-tenant architecture is the right fit, the Totara overview covers the platform’s full capability. For those already running Totara who are looking specifically at the B2B eCommerce layer, Accipio One Shop is the starting point.
As a Totara Platinum Partner, Accipio has deployed this architecture across some of the UK’s largest commercial training operations and can advise on configuration and different commercial models from years of direct experience.