Briefly: Please add a "Folder" tile type that can group tiles together. Clicking on the Folder would show the contents of the folder, similar to the home screen.

Background: We have a large number of Tiles. There are several Product Integrations, a couple RSS, several AEKs and lots of Static Content. And we've only scratched the surface of what our individual department does. To expand to the entire university, we're going to need some way to group these together at least one step below the Home page. A similar User Interface exists on mobile devices to group multiple apps into a Folder, which has a custom label.

As far as we have access, there are no workarounds that would allow us to have a Product Integration live tile that does not show on the home screen, but which can be linked from elsewhere.

Currently for attendance check-in we allow validation by either crowdsource (beacon) or IP address. This works fine when students are using the native app to check-in (even if they are required to enable Bluetooth on their device). However, when they attempt to check-in via the web portal they are prevented from using the check-in with a message of "Please use the mobile app in order to check in".

This is because the web portal doesn't support Bluetooth. But as we also allow IP validation it would be incredibly beneficial to students if they could check-in via the portal (using just the IP validation). This is because not all students have smartphones or some who do have locked down phones which don't allow installation of the native app.

As we look to offer features that serve more focused user groups we find that the creation and management of roles gets more and more complex.

Rather than make an existing role nested (e.g. campus > year of study), we have to create multiple variations (e.g. campus + year one, campus +year two, campus + year three etc). This can lead to a lot of roles and makes it very difficult to manage - if we were to set up roles for each year of study, across 6 colleges, 3 types of study and 4 campuses in the current structure it could lead to over 300 roles.

Allowing role nested or some other way of better managing them would not only be easier but also encourage more ambitious use of the platform.

We currently utilise the CampusM native in-app browser for our LMS system, and we are finding several functionality lacking/not supported with the in-app browser.

Our LMS system allows for:
- Downloading of video lectures to the user's local device
- Downloading class materials to the user's local device
- View captured videos lectures at different playback speed

The above is currently not possible with the in-app browser and we generally find an external browser to provide a much richer experience for our students, our LMS team can provide confirmation that all major external browsers works best with our LMS system. But our institution decided to continue working with the in-app browser for the sole reason of SSO.

Can we improve the product to enable the native app to pass SSO to external browsers? If this is a security risk, can we at least pass usernames across to an external browser so the students will not need to enter their entire login information again?

As a academic I can only check-in students who are timetabled in the specific instance of a timetabled activity. I would like to be able to search for, and check-in students who have attended the class but are not in timetabled class list so that I dont have to keep a manual record when a student swaps from one instance of a session to another.

Example: A course with an enrollment of 250 students might have one lecture and 10 tutorial sessions which in many cases are taught by multiple tutors and may be on different days. A student will be timetabled in the lecture and a specific tutorial, however it is common occurrence where for a specific instance a student may not be able to attend the session in which they are timetabled and will agree with the tutor to attend a different session instead.

Currently the only way to programmatically support this is for the students timetable to be modified in the source system to reflect this change. This is a viable option if the student is wanting to make the change on an ongoing basis, but not practical for a one-off swap.

The current business workaround involves staff keeping a manual record and retrospective getting the allocated staff member to check the student into the session they were timetabled. Manual records are what we are trying to avoid.