campusM 2026 May Release Notes
Developments
Multiple Calendars from Outlook Calendar Supported in Timetable Product Integration
The Outlook Vendor in Timetable Product Integration, which previously only returned the user's default calendar, can now return events from all calendars shared with the user. This can be enabled in the Timetable PI configuration page. For more information, see Timetable.
Task Board Redesign
In a continuous effort to improve productivity and organization, the Task Board Product Integration user interface has been redesigned. The improved Task Board Product Integration now allows institutions to customize colors and aims to increase student organization and productivity.
campusM will start collecting anonymized analytics data on Task Board usage with these UI changes. The data will be displayed in the Analytics section of App Manager starting late summer 2026. Engagement analytics are collected for each university-created task, while user-created tasks are aggregated.
For more information, see Task Board.
.jpg)
Home Page and Web App upgraded to React 19
The campusM Home Page and campusM Web App has been upgraded from React 18.3 to React 19.2, which is currently the latest version of React. This change fixes some outstanding accessibility issues, and generally brings infrastructure up-to-date, making the campusM platform more stable, easier to maintain, and quicker to develop.
For more information on React versions, see the Versions page on the official React website.
Customers using custom CSS and Javascript on the Home Page are strongly advised to test for regressions in the May 2026 Preview environment, with a special emphasis on sidebar behavior, as the sidebar has been significantly restructured. No action is required for customers who do not use customer CSS and Javascript on the Home page, and no UI change is expected for end-users, aside from accessibility improvements.
Customers using AEK are strongly advised to test their code in the May 2026 Preview environment, with a special emphasis on TileSDK integrations. No action is required for customers who do not use AEK.
Various TileSDK projects have been tested internally, and it has been determined that customers using the TileSDK as designed should not experience any issues. However, TileSDK behavior might experience regressions if it has dependencies on third-party code that is no longer supported in React 19.
For more information about migrating your code to React 19, see React's migration guide.
For further support on this topic, please join the campusM Slack Channel.
Permissions for Attendance Configuration in App Manager
A new permission has been added to campusM for Attendance – Attendance: Can Access Attendance Configuration.
Previously, only campusM users with All Permissions checked could access Attendance configuration in App Manager (provided Attendance was enabled for their organisation). Now, to access Attendance configuration, administrators must have either: All Permissions checked, or both Attendance: Can Access Attendance Configuration and Service : Can change product integration permissions selected.
For more information, see Configuring Attendance.
Bug Fixes
| SF number | Platform | Description |
|---|---|---|
| N/A | Mobile | When users navigated to the Moodle PI and then navigated back before completing the Moodle login, a spinner screen showed instead of the campusM Home Page. This was fixed. |
| N/A | All | In certain scenarios, favoriting a subtile from inside an admin container sometimes did not behave as expected. This was fixed. |
| 08126560, 08320086 | All | RSS Feed tiles will now display items in reverse chronological order – from newest to oldest. |
| N/A | All | In the Task Board, when using the Configuration vendor, in some cases it was possible to save a Task without a Title, or a Task with a Start Time and no End Time. This was fixed. |
| 08212623 | Mobile | In some cases, when authenticating via an external browser on a mobile device, App Roles were not applied to users as expected. This was fixed. |
| N/A | Android | The heading in the Biometric Lock screen was not formatted as such, making it difficult for users with screen readers to read. This was fixed. |
| N/A | Android | Upon login, after a user chose to enable a biometric lock for the app, but then canceled before completion of the flow, the Try Again button appeared overlaying an image, making it unreadable. This was fixed. |
| N/A | Mobile | Accessibility for campusM Maps was improved on mobile for screen-reader users. |
| 08269387 | iOS | In some cases, users on the iOS app had to reauthenticate when viewing content through the campusM browser. This was fixed. |
| N/A | Mobile | The accessibility of Tile Containers on mobile was improved for screen-reader users. |
| N/A | Mobile | The accessibility of the search bar component in the Events PI was improved for screen-reader users. |
| N/A | Web | The click area for the radio buttons in the Advanced Role Notification screen in App Manager was too wide, causing mis-clicks. This was fixed. |
| N/A | Mobile | In some cases, subtile text inside of tile containers was truncated after one line when the tile container was 2 tiles high, which is unexpected. Now, this will only happen in certain cases when a container is 1 tile high, as designed. |
| N/A | Mobile | In List View of the Arrange functionality, disabled buttons were focusable, and some buttons were not announced correctly when using a screen-reader. This was fixed. |