The new fingerprint functionality allows you to enable/disable fingerprint sign in to the app, based on the fingerprints stored in your mobile devices (if available). The annoying behavior for this, is that it will ask you to re-fingerprint every time you get back to the app (e.g. switch to another app, and get back to CampusM 2 seconds later re-triggers fingerprint).

Please allow for a configurable time-out timer during which re-authentication with fingerprint will not be necessary.

Changes to AEKs currently require modification from Ex Libris. It would be helpful if AEKs would for the content-part of the pages would become manageable from within the App Manager. This would allow customers to modify text, edit links, change background pictures etc. without affecting the Integrations of the AEKs.

Please look into the possibility of optimising the notification functionality, so that notifications can easily be sent to individuals based on name / Id / e-mail address, rather than groups. The only way to currently do this is to manually search for a name / e-mail, and add users 1 by 1, but we'd like the ability to do this as a bulk add, based on a list of multiple inputs.

Currently push notifications can either be enable, or disabled. If they are enabled, then ALL notifications are pushed (i.e. showing up on lock screen), if disabled, then ALL sent out notifications are in-app notifications (only showing in the tile counter when you open the app). It would be good to have a setting while creating a notification where you could select to either send it out as a push notification, or send it out as an in-app notification.

there is currently no way to remove or hide the native search, share, or feedback functionality. We would like to have the ability to remove or hide these native functionalities altogether, as the University has its own search and feedback mechanisms. Having these native CampusM functions always visible increases confusion with students, and ensure difficulty with our business processes, as we have to manage more different sources/functionalities for students.

Deploy Google Analytics with Tag Manager to CampusM Native Apps, Live and Dynamic Tiles.
- Improve Implementation Speed
- Flexibility
- Custom timelines
- Version Control
- built-in triggers

Can we make Logout button more obvious in Android app settings?

As opposed to personalisation options (the order of the icons) being lost when the user logs out, it would be better if they were associated with the user accounts and kept the icon order when the person logged out and back in again, as opposed to them having to rearrange.

As well as lecture title and time, show the lecture location on the live tile for timetable - this way students may be able to attend the upcoming lecture/event with only the glance from the home screen.

have an alternative dark theme (e.g. Youtube etc..)

Would be useful if we could access the folder of assets to do `git init` etc, so ftp or css access the location of these files. For better control over versioning of files lik css.

We have had several discussions with campusM about the terms of use. It is not ideal to have users accept the terms every time they log in. We would like this to only happen during the first login process.

As many institutions have their own support desk, there's a growing need to integrate the feedback function in CampusM with these ticketing systems or allow admins to hide from view, so CampusM isn't creating an additional stream of support calls outside of the main system.

Students at home for holidays would like to be able to force a selectable/UK timezone for their calendar.

Hide a tile based on a role.

I often get asked to hide tile based on role membership such as "first year students" or "final year students".

For example we use the timetable tile but some courses don't have a timetable and we would therefore like to hide the timetable tile for those students (who are easily identified by course).

Detect current version of app and prompt users to download latest version when opening, (either optional or required) to continue using the app - with message to explain why they need to upgrade (potentially editable by institution).

Would be useful when we've had recent updates to key services/tiles that are not being realised by students with manual updates, whilst ensuring consistency of experience for all.

Wouldn't it be great if we knew how many clicks banners go? How successful is a campaign?

In Creative Studio the template library should be restricted so that editors can only see and use the branded templates that institutions have created.

The drag and drop elements should be restricted as well to only show our branded components.

Currently, if the connect layer encounters an error while retrieving data, it passes back an HTML file with an HTTP 200 status code, as in the example below. It would be helpful if instead it would pass the error back to the client directly, with error messages and HTTP error status codes, as a normal web server would.

<!DOCTYPE html>
<html>
<head><meta http-equiv="content-type" content="text/html;charset=utf-8"></head>
<body data-location="/aek/c/dining-menu">
<div class="ombl---ajax-container">
<h2>Oops! Something has gone wrong</h2>
<p class="error last-child">Could not resolve host: api.dineoncampus.com.wrong</p>

</div>
</body>
</html>