Create a concern wizard currently allows teachers/staff to create a concern about an individual but stops short of allowing the person creating the concern to add actions for follow-up. Actions are only accessible by entering the full Wellbeing Ma...

Having the carousel displayed on the dashboard of the new Cloud Parent Portal for logged in users does not actually have any benefit for users and takes up screen space. It would be helpful if the carousel could be hidden for logged in users.

In our previous MIS, Administrators could make changes to reports already published/printed. It would be really helpful if iSAMS would allow administrators to edit past reports in a simpler way. Currently we need to re activate a cycle, and change...

I have received some requests from our staff for a "Contact Pupils' Parents/Guardians/Contacts" feature in the Student Manager Wizard Bar, just like we already have the "Contact Pupils' Teachers", but instead one for contacting their parents/guard...

We would like a few selected users to have full access to Email Manager, to enable a corporate approach to our email templates. However, my understanding is that we can't grant this without giving them full access to Control Panel, which we don't ...

We have set up the default contact mail options in Student Manager to be Reports and Communication. This is so that our Finance team can tick billing when they set up the billing accounts. When a record is manually added in Admissions Manager, the...

It would be great if we could produce academic reports and schedule their publication. For example, being able to release reports tonight at 6:00 p.m. Similarly, we would like the same functionality for external exam results—specifically, the abil...

Add a checkbox for 'Emergency Contact' in the Contacts section (similar to the existing 'Student Home' checkbox). In the Parent Portal, introduce an option to display only designated emergency contacts, regardless of their contact type. This will ...

It will be useful to simply hide a custom field instead of having to delete it. I assume by hiding we'll be able to maintain the historical data and also reactivate it if the need arises.

I am posting the following here at the advice of out Account manager. It relates to a number of iSAMS modules and issues we have in applying GDPR principles with the tools provided within iSAMS. Under GDPR good practice we wrote a list of the data...