Summary
This chapter discussed different ways to support Moodle multi-tenancy. We first defined what multi-tenancy is and showed why there is a need for different types of multi-tenancy implementations. We presented three different approaches, one of which hopefully matches your requirements.
The first model, multi-tenancy via categories, used a single Moodle instance with configured course categories and permissions.
The second approach, multi-tenancy via a centralized code base, provided separate standalone instances and delegated all responsibilities to local administrators.
Lastly, we presented multi-tenancy in Moodle Workplace, the most versatile out-of-the-box implementation currently available.
We covered three representative implementations to facilitate multi-tenancy in Moodle. These solutions can, of course, be extended or further modified to cater to your individual requirements. While some aspects of implementing multi-tenancy might look technical, daunting...
