Alert time frame for shift clock-in/outs

[augustalan]

I am finally switching over to using Square for managing employee schedules. We already use the clock-in and clock-out settings integrated in the POS but I am setting up my alerts for shifts when employees clock-in or clock-out. There are alerts for early/late clock-in/outs but it does not specify what time that happens or if those time frames can be changed. Does anyone know how early or late do those alerts trigger?

[VanKalkerFarms]

on this page you can set how early you allow clock ins but I don't know what the default time would be.

https://squareup.com/dashboard/shifts/settings/clock-in-out

[augustalan]

Thanks for surfacing that information. It would definitely make the alert for early clock-ins moot. Still doesn't solve the alert timeline for late clock-in alerts.

[augustalan · Accepted solution]

I believe I have answered my own question but since there isn't any good documentation on it I'll add the answer here.

From this url (https://squareup.com/dashboard/shifts/settings/notifications-and-alerts) in the Staff -> Settings -> Notifications and Alerts page there are a list of alerts that identify alerts going to the Dashboard. My hope was that these alerts would be focused on the admin but these notifications seem to be directed towards which alerts employees can receive.

From the Square Team App under More -> App Settings -> Notifications there are a list of notifications available to be adjusted. One of these notifications is "Clocking in and out". It says "Receive notifications if you haven't clocked in 5 minutes after your start tie or haven't clocked out 5 minutes after your end time."

It seems that this alert lines up with the alert in my original question related to Early shift clock-outs and Late shift clock-outs.

There are no pop up notifications that go to anyone else around late clock ins. The alerts in the page linked above in the Dashboard are focused instead on the alerts that show up when you are viewing timecards.

The problem was solved but unfortunately it does not give the desired answer but that becomes a feature request not covered by this topic.

Thanks for reading everyone.