Table of contents

• Release Schedule
• Open LMS Mobile App version upgrade
• Conduit is now fully available
• New Personalized Learning Designer (PLD) Module Now Available
• New Plugins

The Open LMS Product team is pleased to announce the release of WORK 4.5 MP4:

Release Schedule

• Saas Sandbox Upgrade: Tuesday, August 19, 2025

• Saas Production Upgrade: Tuesday, September 2, 2025

• MH Production upgrades can begin September 9, 2025

Open LMS Highlights

Upgrade to Core 4.5.6

As part of this minor release, Open LMS has upgraded its platforms and reviewed the code of Moodle™ version 4.5.6, adding the corresponding fixes, improvements, security patches, and important backports.

Release Notes
For the full release notes from Moodle™, please see:

Moodle™ 4.5.6 Release Notes

Open LMS Mobile App version upgrade

We have updated our mobile App Moodle™ version to 5.0 on iOS and Android devices. You can find it in the Android and Apple stores available for download.

Note: new version is now available in stores

Please visit https://moodledev.io/ for the full release notes.

Moodle™ App 5.0

New in the Open LMS App
Biometric authentication is now available!

You can now log in to the Open LMS mobile app using your fingerprint or face recognition. To enable this feature, go to App Settings > Biometric Settings and activate it.

Enjoy a faster and more secure login experience!

We’re excited to announce that Conduit is now fully available in Open LMS Work!

This means all the powerful data integration capabilities you’ve come to expect from Conduit—including support for user creation, course enrollment, course creation, group and cohort management, and more, can now be used seamlessly within the Open LMS Work platform.

With this update, organizations using Open LMS Work can:

• ✅ Automate user and course management tasks

• 🔄 Ensure accurate and timely data syncing from external systems

• ⚙️ Streamline onboarding and enrollment workflows

• 📊 Maintain data consistency at scale

If you're already familiar with Conduit in EDU, the experience in Work will be the same, no need to learn a new system!

📚 For documentation and implementation guidance, visit:
Conduit Overview – Open LMS Knowledge Base

Conduit Enabled by Default

The full Conduit feature set is now enabled by default to make integration even easier:

• auth_conduit: Provides secure authentication via Conduit API endpoints

• enrol_conduit: Enables user and course enrollments through automated Conduit data feeds

• block_conduit: Offers a user interface for administrators to manage Conduit file processing

These components allow for scalable and secure data operations, reducing the need for manual intervention in routine administrative tasks.

🏷️ Multi-tenancy Considerations

While Conduit does not currently offer full support for multi-tenancy operations, there are a few workarounds that allow you to achieve some level of tenant-specific management:

• ✅ Course creation under tenant categories: You can configure your Conduit file to create courses inside specific tenant categories. This ensures the courses are scoped appropriately and visible only to the relevant tenant.

• ⚠️ Adding users to tenant cohorts: Although Conduit can add users to tenant-specific cohorts, doing so does not assign those users to the tenant itself. Tenant cohorts are protected and cannot be manually modified for this purpose.
  However, we already provide a bulk user upload alternative specifically designed to onboard tenant users correctly.

• 🔄 Use bulk actions to assign users to a tenant
  You can use the bulk user actions to assign users to a specific tenant using the tenant cohort ID. This is currently the recommended method for onboarding users into tenants reliably.

We are actively tracking feedback and use cases related to multi-tenancy and will continue exploring enhancements to improve this experience.

🧩 New Personalized Learning Designer (PLD) Module Now Available

We’re excited to announce that a new version of the Personalized Learning Designer (PLD) is now available as an activity module: mod_pld!

This new module retains the same user-friendly experience for creating automation rules based on events, filtered by conditions, and executed through actions, just like the original PLD.

🔄 What’s New?

By making PLD a module, you gain new flexibility and reusability:

• 📦 Reusable Rules
  You can now back up and restore PLD as an activity, making it easy to reutilize rules across courses by including the PLD module in course backups.

• 🏠 Site-Level Rule Automation
  mod_pld can be added to the site homepage, allowing for rules to be triggered at a site-wide level.

• 🎯 Familiar User Experience
  For those who have used the legacy PLD (local_pld), the interface and logic remain the same so there’s no learning curve.

⚙️ Setup Requirement

PLD depends on the block_collect plugin to collect data used for PLD events and conditions.
Please ensure data collection is enabled via:
Site administration → Blocks → Block Collect → Settings

Without this, PLD rules will not trigger as expected.

🔁 Migrating from Legacy PLD (local_pld)

If you are currently using the older local_pld plugin and have existing rules you wish to migrate:

• When you add a mod_pld activity to a course that already contains non-disabled local_pld rules, a migration link will appear in the header of the mod_pld view page.

• Clicking this will show you a list of existing rules and their current state (active/disabled).

• You can choose which mod_pld instance in the course to import them into.

• After importing, the original rules will be automatically disabled (but not deleted), so you retain a backup.

This new modular version of PLD gives you more control, better portability, and the ability to automate at scale, all while keeping the familiar experience you've relied on.

To learn more about how PLD Works visit this link: https://support.openlms.net/hc/en-us/articles/15360993412252-PLD-Overview-and-Introduction

New Plugins

Updated plugins

Additional fixes and Improvements