campusM
Your feedback matters to us. Help us improve campusM by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
6 results found
-
Add Delivered-Based Engagement Metrics
At present, engagement rates are calculated using the number of notifications sent, rather than the number successfully delivered. This can produce misleading open rates, particularly where notifications are never received because, for example, the app has been uninstalled or the device is offline.
It would be valuable to introduce delivery metrics alongside the existing analytics, allowing institutions to report on:
Notifications sent
Notifications successfully delivered
Notifications opened
Open rate based on delivered notifications rather than total sentWe appreciate that defining what constitutes a "delivered" notification may not be straightforward (for example, where users have disabled push notifications), but having…
7 votes -
Improve Notification Analytics with Audience Breakdown and Notification IDs
We're finding the current notification analytics difficult to interpret when a single notification is sent to multiple audience groups (e.g. students, staff and other users). The results are aggregated into a single dataset, making it impossible to understand how each audience has engaged.
It would be valuable if analytics could:
Break performance down by recipient group (e.g. Students, Staff, Other), rather than only showing combined figures.
Include a Notification ID within the analytics export. This would allow institutions to map analytics back to the original notification, making reporting and analysis much easier.It would also be extremely useful if the…
7 votes -
Display time zone information for event times
It would be helpful to display a brief note or label near event times indicating which time zone is being used, such as “Times are displayed in your device’s local time zone.” This would provide users with clearer context and help prevent confusion when viewing events. This is a pain point for our org.
2 votes -
Outlook Integration: Allow access to all user mail folders Description
In the new Outlook integration, it would be beneficial to extend folder navigation capabilities so that users can access any mail folder available in their mailbox, including custom folders they have created themselves.
Many users organise their email using personal folder structures for projects, courses, departments, administrative processes, and other activities. Providing access to the full mailbox folder hierarchy would allow users to work more effectively within CampusM and access all relevant email content without having to switch to another application.
The legacy Outlook integration supported access to any mailbox folder. Including this capability in the new integration would help…1 vote -
UX enhancement: Make return‑to‑today action more obvious on Timetable/Calendar
Although the functionality exists via the calendar icon, it is not very discoverable, and users may not realise that this is how they can return to today’s date.
It would be helpful to introduce a clearly visible control (e.g. a “Today” button) to allow users to quickly return to today’s date, similar to the behaviour in the iPhone Calendar or Microsoft Teams mobile calendar (see attached screenshots: iPhone Calendar on the left, Teams Mobile Calendar on the right).
1 vote -
Support Ellucian Web API Version 2.0+
Ellucian is no longer supporting Colleague Web API version 1 as of 6/26/2025 as stated here: https://elluciansupport.service-now.com/customer_center?id=community_Blog&sys_id=d6c7848183126a10926912d0deaad33e
CampusM delivered integrations relying on Colleague Web API connections is not functioning correctly on Colleague Web API version 2.0+. The integrations having this issue includes Timetable and Holds. After speaking with the ExLibris support team, there is currently no plan to support version 2, however we need to have the integration updated for security purposes. Please add support to Colleague Web API version 2.0+
6 votesDocumentation has been provided over a separate channel. This idea will be reviewed by our R&D team, and will move on from the "Under Review" status in no more than 6 months time.
- Don't see your idea?