Ideas

When exporting Consent Register responses, all pupils (current, applicants, and leavers) are included by default, and there is currently no option to filter them out before export. It would be helpful if these groups were excluded by default, with...

An API endpoint to support integration with third-party systems so consent data can be managed and synced across multiple platforms making it accessible for all relevant stakeholders.

Please include students' full First Name, Last Name, and iSAMS ID in Consent Register exports. Currently, only the first initial and surname are shown, which makes it difficult to identify students with similar names and requires additional manual...

Currently, Consent Registers are only available for parents of students below 16. Ideally, we would like parents to be able to submit consents for students till they're 18 instead.

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

Let users first select the location to filter the supplier list when raising req/po etc. Relevant for users who have access to multiple locations, mainly Central teams. Makes it easier to find a location supplier, rather than scrolling through 20+...

Once an order is approved it cant be amended. If an order is raised against the wrong nominal code this creates a commitment against the wrong nominal code and wrong budget line. This cant be corrected while the invoice has been received. Can cert...

When we raise a REQ we can add an attachment but when we convert that REQ into a PORD the attachment is not carried forward onto the PORD. We use this for quotes etc. What we would like is for this document to appear at every stage up until INV. A...

Display original details in a greyed-out section above the fields for reference. Easier to see what they original REQ vs PO vs GRN vs INV looked like without coming out and back in again

Show a warning if the invoiced quantity differs from the GRN quantity, if further invoices are expected or not. If not, then potential auto-write off for remaining