Ideas

We have three parts of the school, Pre Prep, Prep and Senior, but I can't view all the cover needed across the entire school on one page, only one page for each section. If there was a way to show all cover needed in the day across the entire scho...

There is a section in Leaver Information in Pupil Manager to select the Progression Year Group and the Destination. We would like to be able to post data to these fields via an API.

It would be a good if employee working patterns were visible in the directory. This would allow staff to quickly check who is scheduled to be in on a given day, if they have the right permissions.

Frequently when cover is required due to part of a year group being out on a trip, we may combine classes. We couldn’t find an obvious way of combining classes and notifying teachers that this has happened. We found that we could get the same memb...

We would benefit from a quick add option in the cover module. I would have the opportunity to create an "absence" add a name and the time required. It would be great for invigilation and random duties we need to cover. It would generate a cover sl...

Additional fields for the criteria of entitlement groups would be a useful feature, for example all those on a fixed term contract or who have a particular amount of working weeks in their record.

Currently, there is no method to activate or deactivate a staff member via the REST API. Adding support for this feature would be highly useful for HR and IT teams who manage staff lifecycle through automated workflows or external HR platforms. By...

We have an existing integration with Digistorm CRM and need these two frequently used fields to be available for integration on Applicant endpoint. Recently, due to compliance requirement on invoicing, these are now mandatory and without an integr...

it would be useful for expired courses i.e. KCSIE 2024 could be deleted from the central course library, regardless of staff completing the course.

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.