Notifications on the Mobile App
Push Notifications can be sent, received, and acted upon from the Mobile App.
A user will receive notifications on the mobile app if the following is true:
- The user has Notifications turned on in the Mobile App
- The user’s Notification Profile has the “Mobile App” destination selected in at least one of the three priorities.
All of a user’s notifications are present in the Control Center from the app. When a notification appears on the app, tapping the notification will bring the user to the Control Center (after logging in, if necessary).
Actionable notifications
Notifications on the Mobile App contain "actionable" options that vary according to the type of notification.
For example, certain notifications can be acknowledged ( Mark Done ) right from the notification. Other notifications allow the user to immediately act on the notification (such as Approve a timeoff request or Refuse a shift swap request) without having to log in. A Go To option, when tapped, will direct the user to the relevant location in the system. If the user is not logged in when tapping Go To, login is required before the redirect happens.
In order to perform an action, the user must be set up with access. For example, if a user selects the action to "Punch" but does not have access to the Punch Tile, a blank screen will appear with a message indicating that 'you cannot access the punch tile'.
When push notifications are sent to devices, recipients can take specific actions depending on their role. Actions are either simple or advanced. Simple actions include Punch, Time Off Request, Mark Done, Delete, and GoTo. Advanced actions include Approve and Refuse. These advanced actions are only supported on the Mobile App for the following notifications:
- Availability change
- Missed Punch
- Open Shift Request
- Open Shift Available
- Overtime Reached
- Overtime Approaching
- Shift Swap
- Time Off
- Unexcused Absence
When a notification is acted upon from the app, a Submitted message indicates only that the action has been successfully submitted to the server. The server then processes the action. This is an important distinction because, for example, you may approve a timeoff request from a notification and get a Submitted message on the app. If that request you approved had been deleted by the originator, the approval would reject on the server.
Note that when a notification appears on the app, the notification resides on the app, independent of the server. The notification will remain on the app until acted upon in the app.
Allowing notifications
When you log in to the app for the first time, the system determines if your Notification Profile has the "Mobile App" destination selected (for any priority).
In this case, you are prompted to “Allow Notifications?”
- If you allow notifications at the prompt, a “Notifications” (or "Allow Notifications") item will appear on the App Settings on the device – enabling you to turn notifications off and on.
- If you do not allow notifications at the prompt, the prompt will repeat when you log in for the fifth time. The prompt will not reappear after this.