Student Manager

We are required to keep all current and previous address details for any pupil on a Sponsored Visa. The current suggested way to do this is via the Notes section within Contacts but it should really be possible to either maintain a proper, searcha...

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.

Being able to enter university destinations for leavers is a good feature, but it is not a field that is available to pull out on any export, nor is that a standard report. It would be useful to have it as part of student export, but also searchab...

We have entrance exam results for each pupil in spreadsheets for each yeargroup, which we are considering adding to the Entrance Exams section on the pupil records. We can either enter all the results manually (which would take some time...), or s...

We have all kinds of families at our school as I imagine most schools around the world do. In 2025, in Education (and most other sectors) diversity and inclusion are highly valued, all families deserve to be represented. Same gender families and b...

At present we use a user's "Security Profile" to control who has access to Pupil Manager module in iSAMS, and the level of access (read/write/full/etc.). When it comes to setting the granular permissions within Pupil Manager, this is done based on...

We should be able to upload a photo against each contact in the same way that we can against staff and students. These should be available via the API and other reports.

An attachment could be use to supplement an email body's content like include further instructions. Having to attach an identical file each time a particular e-mail template is used limits e-mail template usability and appeal.

There are some fields within the system that are either not relevant to our setting (e.g. Boarding House) or that we do not use (e.g. School Age) that we would like to be able to hide/remove from the user interface to make the system easier to use...