Ideas

When new accounts are created, currently, Admins need to enable 2FA on the account manually. This can lead to ad-hoc accounts not being protected. In today's climate, it is much more likely that an organisation requires 2FA and will disable it for...

If you own more than one product, it automatically logs into Compliance. It's confusing for staff to have to switch. Having HR as their landing page would be far easier

In the job details section, it would be helpful to have a paid leave carry over field as well as the paid leave entitlement field. This will enable us to enter the employees standard paid leave entitlement without the need to adjust each year. We ...

Customers want to report on all different types of data for various reasons, but not all data fields are available in the report builder or in the pre built reports. Giving them the option to choose any field that they have populated with data and...

EveryHR is currently generating Leaver Notifications for employees where a specific role is ending. We would only expect Leaver Notifications to be generated when an employee’s Employment with the Trust is ending. As this is causing confusion with...

Platforms like Wonde and Groupcall have fields ready and waiting for the pupils' 'preferred surname' and 'legal surname' data, but iSAMS only currently presents the legal surname to the api.Please can the preferred surname be added as a field avai...

Is it possible for us to have 'post category' added on to the built in all absence instances report download please? The one that says if a staff member is support, classroom, leadership. Knowing how many teachers, support and leadership are off s...

The ability to distribute Objectives across performance records would be a great tool. Especially for Department Heads or CEOs that would like to subject SLT to the same consistent Objectives. Currently this has to be done per Performance Record

Current Issue: Self-service users of the Time and Expenses module can submit expense claims using general names such as "September 2025 expenses" and also may group multiple expenses (e.g., food, fuel) under one claim. This creates challenges for ...

The API does not support deletion of sickness through the REST API. meaning we can only sync the creation of a sickness from our HR platform to iSAMS as well as updates, but if a sickness request is deleted in our HR platform we have no way of del...