Update pupil audit record for all with shared contact
I have updated the country on a parent record. This has been correctly recorded in the audit trail for this pupil, however there is no audit record for the sibling, and their contact was also updated. If a change is made to a contact record, it wo...
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.
The DBS issue and expiry date can be populated in the pre employment tab of the employee record. Please can you think about adding at least the expiry date as a column to the SCR report. . This is the report I would download for an OFSTED inspecti...
Having a total of how many parents/guardians/contacts are in the system currently
Having a total of how many parents/guardians/contacts are in the system currently would help give information to third party providers who link the information to different softwares. At the moment we have to run an export but because we have pare...
It would be useful if customers were able to import pay elements against multiple employees. Currently employers have to enter against individual records, which can be time consuming if there are significant volumes. For example, customers may hav...
Consistent use of groups for setting permissions throughout iSAMS
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...
Ability to remove or hide built-in fields which are not used
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...
Allow any changes made in Every HR, from absences, contract changes and address changes, to be synced back into Arbor. Any changes to Arbor to be reflected in Every HR after the initial sync.