Issue
- I have an employee who is not able to clock in
- Why is an employee unable to clock in for their shift
Environment:
- Push Web App
Resolution
Position: In order for an employee to clock in, they need to have an active position. If an employee doesn't have a position, you can use this article, How To Assign An Employee A New Position, to update the employee's profile. Once this is done, the employee will be able to clock in
Clock Settings: If the following feature is enabled: Prevent clocking in when an employee is unscheduled. Employees who are not part of a published schedule will not be able to clock in for their shifts. You can use this article to review and disable this feature toggle, How To Update Clock Settings
Clock ID: If an employee does not have a Clock ID they will not be able to clock in regardless if they have an active position. You can use this article to update the employee profile to have a Clock ID, How To Edit An Employee's Information
Position Access: If you are filtering what Positions have access to clock in and out from the Push Time or Push Employee app, employees may be unable to clock in if their Position does not have access. You can use one of these articles to assist you with reviewing if you need to update the Position access, How To Filter What Positions Can Clock-In/Out From The Push Time App or How To Filter What Positions Can Clock-In/Out From The Push Employee App
Additional Information
We recommend reviewing the above to ensure that your employees can track their worked hours through Push.
If you are still having trouble, please contact the Push Support Team at support@pushoperations.com to best assist you. We recommend providing the employee's first and last name, their Position, the Device ID from the specific app that is preventing them from clocking in, and/or a video clip of the employee being unable to clock in.
Please note that Super Administrators and Team Administrators with the proper permissions will be able to make these changes.
Related Articles
Comments
0 comments
Article is closed for comments.