Ideas

Most schools have a required social media check as part of the SCR. It would be good if this was built in to the system as a default check rather than having to be built in manually by every school using the 'Other checks' feature.

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

Currently, the SCR is fully compliant for state schools. Further enhancements are required to make this compliant for independent schools. Current workaround is for the school to add in additional checks themselves, instead of the checks being the...

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