Ideas

Would it be possible to have the Update Data or Save Data button on the page rather than on the different sections in Student Manager and HR Manager? For example - we have 5 sections in Student Manager > School tab, including custom fields/sect...

It isn't currently possible to temporarily save a written email in email wizard while working on it: as soon as you go to another tab your work is lost. Allowing a draft to be saved would be a huge help.

The ability to add hyperlinks or URLs into a student custom field, therefore allowing the emailing of individual and unique 'clickable' links to each student/parent through iSAMS email wizard.

Title This field is not fully compatible with iSAMS. While all Applicaa data list titles as either Master (male) or Miss (female), they appear as Mr (male) and Ms (female) in iSAMS. Parental Responsibility When importing from Applicaa, parents are...

Need a way to capture stepparents under Family - assuming one parent has remarried/deceased and one biological parent is no longer actively involved.

This is a feature I have discussed directly with our account team but worth capturing here as well for wider input. Currently in Registration Manager > Report tab, the pupil filters do not include the ability to filter by pupils on particular r...

Could Next Year's Academic House be added as a merge field for the email wizard in Student Manager. This would be useful for informing our Year 6 pupils of their new academic house when they move up to our senior school. It would also be useful fo...

To be able to add more than one email or contact number for parents on the student details would be really useful. Most parents have both personal and work details that they provide but we cannot enter onto ISAMS.

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

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.