Moodle Plugins directory: Multi-tenancy | Moodle.org
Multi-tenancy
Experimental ::: tool_mutenancy
Maintained by 
Petr Skoda
Petr SkodaMulti-tenancy plugin for standard Moodle™ LMS installations. Requires the MuTMS core patch, included in the MuTMS distribution.
Latest release:
83 sites
1k downloads
22 fans
Current versions available: 4
This plugin introduces multi-tenancy to standard Moodle™ LMS installations — fully open source under GPL 3.0, with no restrictions on commercial use. Requires a small core patch included in the MuTMS distribution.
The plugin is listed in the Experimental category solely due to the core patch requirement — it is production ready.
Multi-tenancy allows a single Moodle instance to be partitioned into isolated tenants, each with their own users, roles, courses, appearance, and settings — making it possible to serve multiple independent business units or client organisations from one installation.
Features
- Tenant management — create, configure, and delete tenants
- User isolation — users are scoped to their tenant and cannot access other tenants
- Tenant-specific roles and permissions
- Tenant-specific appearance and branding
- Non-intrusive design — standard Moodle features and workflows remain fully functional
- Fully uninstallable — removing the plugin does not affect the rest of your Moodle installation
Typical use cases
- Multiple independent business units or departments on a single Moodle instance
- Client or partner training portals with separate branding and user bases
- Franchise or reseller networks requiring isolated learning environments
Installation
MuTMS core patch and this plugin are included in the MuTMS distribution.
You can also install it manually from git repositories:
- Apply the multi-tenancy patch to Moodle™ codebase
- install Additional tools library plugin
- Install this plugin
- Install or upgrade the site
- Login as site administrator
- Activate multi-tenancy in Site administration / General / Tenants
- Start creating tenants and member accounts
Roadmap
- Universal catalogue — tenant-specific course catalogue
- Tenant separation improvements
- Moodle Mobile App support improvements
Screenshots
Contributors
Petr Skoda (Lead maintainer)
Please login to view contributors details and/or to contact them
Best regards,
Are tenant-wise subdomains and course-sharing on the roadmap. Actually, have used IOMAD for a previous client. Would this be a better approach going forward?
We are currently evaluating the Multi-tenancy plugin in our Moodle environment and have encountered a couple of issues that we would appreciate your guidance on.
Single Sign-On (SSO) with Multiple Tenants
It appears that the plugin does not fully support configuring separate OpenID Connect (OIDC) / Microsoft Entra ID SSO providers for different tenants. Since the OIDC configuration is global, we are unable to assign different Client IDs, Client Secrets, and endpoints to individual tenants. Is multi-tenant SSO with separate identity providers for each tenant currently supported, or is this a planned feature?
Tenant Branding
We have also noticed some limitations when configuring branding for individual tenants. In some cases, tenant-specific branding (such as logos, colors, and other branding settings) is not applied consistently or does not behave as expected. Is this a known issue, or are there any recommended configuration steps or best practices to ensure tenant branding works correctly?
We would appreciate any guidance or recommendations you can provide. Thank you for your support.
separate SSO support for individual tenants is not implemented yet - it is technically doable, but I was delaying the implementation because I wanted to try implementing a new SAML2 auth plugin first.
I am not aware of any known issues with tenant branding, please report everything with replication steps via GitHub and I will address those issues as a priority.
Thanks a lot for your feedback!