Multi-tenancy
Tenants are isolated entities with their look and feel, structure, users, and learning entities. They are critical for when you wish to represent multiple self-contained business entities in your organisation.
Multi-tenancy has been implemented as a single instance of Moodle Workplace that serves multiple client organisations (tenants), where its data and configuration are virtually partitioned, and each client organisation works with a customized virtual application instance.
Multi-tenancy is the ability to enable the configuration for multiple tenants with different themes and permissions, keeping them separated so that users in one tenant cannot see the users in another. Each tenant has its own users, hierarchies, roles, dynamic rules, theme settings, reports, and learning entities (courses, programs, and certifications).

The overall multi-tenancy architecture of Moodle Workplace can be summarised as follows:
- Site-wide features are global and apply across tenants
- Tenant-aware features can be configured for each tenant
- Each user belongs to a single tenant
All Moodle Workplace tools are multi-tenant-aware - depending on the features, different levels of multi-tenancy are supported.
Privacy considerations
All user information from each tenant is stored in the same database and table. However, by default, no personal data is shared between tenants, and each remains unaware of the others. This design aligns with Moodle’s commitment to GDPR requirements for data protection by default and by design.
Administrators can choose to enable sharing between tenants, allowing users to see others from different tenants. This includes visibility in forum posts, course participant lists, gradebooks, reports, and other modules that display participant information.
Certain professional or institutional bodies may require that data not be stored alongside that of other entities. If physical separation of tenants is required, multi-tenancy may not be suitable, and separate Moodle sites may need to be set up.
