All ideas

It would be useful to be able to pull off a report of staff who haven't taken any time of for sickness over a chosen period of time as this is a big achievement.

When you get an authorisation email from someone, rather than clicking on the link and it taking you to the dashboard, it would be helpful for it to take you straight through to authorise it.

Each time a Ripple sends a reminder to do something, it should automatically update the system without the person also having to then go into Tasks and mark as completed.

Is there a way to report on the sickness % that you can see on the employees planner top of screen with queries. We can't seem to find where this outputs to so we can report on Sickness Absence rather than having to take this and complete calculat...

Please can you add the option to include Public Holiday template and Work Pattern as fields in the CreateNewEmployee API method. Public Holiday template is a column in the Excel import template but not available in the API. When loading employees ...

It would be helpful to be able to filter the employees in the outlook calendar feed from the planner section to only the individuals/locations/departments that you have specified at the top. Currently the feed takes all staff details across to out...

When bulk adding holidays to all employees planners (we do this for our Christmas closure dates) the default settings include people who have an upcoming leaving date even if the holiday booking is after their leave date. It would be helpful for t...

With our payroll being monthly, it's an irritant for our Supervisors to have to authorise timesheets weekly, and not monthly. We only have a few on worker contracts - but we all get paid the same date. Can we not have the facility to sign off time...

It would be extremely helpful to increase the API capabilities to enhance the possible integrations. For example, adding the ability to add emergency contacts and bank details via API would be very helpful.

When marking leavers, admins are forced to add supporting comments in when staff are 're-employable' but are not forced when staff are 'not re-employable'. Surely this should be the other way round. Admins are wasting a lot of time adding comments...