Note: Requires PHP 7.4 and higher
Based on MoodleTM 3.11.4 - the base install now includes a few plugins natively that previously were installed separately.
Installed automatically:
tool_olms_tenant
local_olms_work
mod_facetoface
auth_saml2
theme_olms_work
local_catalogue
Recommended to be installed
mod_coursecertificate
tool_certificate
block_configurable_reports
enrol_coursecompleted
format_tiles
local_boostnavigation
Other plugins may work, but may not have been tested against multitenancy. The listed certificate plugins are the ones that support multitenancy and are targeted for enhancements as new WORK features are released (such as programs and certifications).
Functionality available now
-
Tenant creation
-
User self-registration or manual authentication per tenant
-
Bulk user upload per tenant
-
Per tenant branding in a Boost-based theme (logo, favicon, color and css) - in 1.0.2 these features have been ported from Boost to the new WORK theme.
-
Per tenant certificate templates (by default users with tenant manager role can create them within their tenant)
-
Lite programs - courses can be grouped together with access to each course dependent on completion of the previous course. A visual indication of this linkage is created automatically (supplied via enrol_coursecompleted - if installed)
-
Live event registration and session management
Roles changed and added by WORK
On install the following permission is removed from the authenticated user:
View course category and courses within it
moodle/category:viewcourselist
Three roles are added by default:
-
Tenant user (category context)
-
Tenant manager (category context)
-
Tenant admin (site context)
When a user is created in a tenant the tenant user role is assigned in the category context for the category affiliated with the user. When a user is assigned as an administrator of the tenant they are assigned the tenant manager role in the related category and the tenant admin role in the site context. Both of the category level roles include the moodle/category:viewcourselist permission in the category context - this is how users are limited to viewing only their own courses.
If a client is not going to be using multitenancy you can restore moodle/category:viewcourselist to the authenticated user definition.
Note: Currently it isn’t possible to completely disable multitenancy. All users must exist in the default tenant for site functionality to work. This means the user creation process must work with tenancy or at minimum add the users to the default tenant correctly.
Comments
0 comments
Article is closed for comments.