Ideas

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...

The ability to manage pages at MAT level and view analytics & ofsted compliance in a summarised view for the group.

Currently schools cannot do partial refunds and are ONLY able to refund against transaction lines - feedback has been that this is a relatively rigid model, especially with partial refunds not being available.

At present there isn't a link back into admissions or pupil manager from the data protection module so when running searches on who we have consent to email about an event, we can't do it through either (any) portal.

The Details field is what appears when requesting consent, so it would be good to able to add clickable links to the text, e.g. to the relevant data protection policy...

It would be useful for a user to receive an automated notification when a consent is changed on one of the registers on the Portals.

The consent age required by Luxembourg Law is 18 but the system is limited to the age of 16. Could you add a search field so schools can choose what consent age they require. Also, if you change this could you change the wording on the Consent For...

During the Export Consent Register Responses process it would be useful to add a Student Status filter. This is so that "Current" could be selected so that when exporting the responses only current students are exported.

It would be helpful to be able to filter the access to different consent registers, so that only the filtered groups have access to complete the consent register from the portals, and for just groups of pupils to be included in the relevant consen...

It would be helpful if batch methods/endpoints were available to allow us access to the consent fields in the data protection module, in particular the pupil photo consent data