Mobile: Late punch notification for managers
Updated
by
Daniel Sjögren
It's now possible for a manager to receive push notifications in the mobile app when employees haven't punched out from a shift at the shift's end time or punched in at shift's start time. There are some parameters that rule how the notification works. The settings for this function are located in the Settings tab in the mobile app.
The following settings are available:
- Choose whether you want to receive a reminder each time an employee has a punch that has gone over the shift's start time, end time, or both.
- Set how long of a time period after the shift's start/end time you want the reminder to be triggered. it's possible to choose this in increments of 5, 10, 15, 30, 45 minutes and so on up to 3 hours.
- Choose whether you only want reminders about people who are working in specific units (from the units in which you have a manager role). By default, you always have all units you have a manager role in selected, but you can de-select and choose specific units you want to be notified about, for instance, you only want to be notified about three units out of ten.
- Choose whether you only want a reminder of employees who are working specific shift types. By default, you always have all shift types selected, but you're able to select specific shift types that you want to be notified about.
Preconditions
- The logic will only send a notification if the manager is actively working that day (has a punch in progress).
The logic for which a manager receives notifications about late punch in/out follows the same logic as shift booking notifications.
- The manager has write access on permission "Schedule".
- If there is at least one manager role in a group above the employee's highest role on the unit tree where the shift belongs. (The definition of a manager role in Quinyx is ALL roles except the employee role).
The notification will go to all managers on a unit (or section) where the shift is located with one role above the employee's highest role AND with write on permission "Scheduling". The logic looks upwards in the role and group hierarchy until it finds at least one manager to send the shift booking/swap request to. If there is no manager role one level above the employee's highest role in the unit/section where the shift is located, the logic looks two levels up, three levels up, etc. in the unit tree in the role and group hierarchy where the shift belongs until it finds at least one manager to send the shift booking/swap request to.
Read more about the shift booking notification logic here.
