Hi! I see that your IP address changes are causing issues with clocking in on OnTheClock, and you have to manually update the IP each time. Let’s look into this so you won’t have to do that anymore.

Typically, OnTheClock can restrict clock-ins based on IP addresses for security. If the IP address of your device changes frequently (which happens often with certain internet providers or networks), this can block clock-in attempts.

Here’s what I suggest:

1. Use Multi IP Range Enforcement: Instead of restricting clock-ins to a single static IP, you can allow clock-ins from multiple IP addresses or an IP range. This way, if your IP changes within that range, the clock-in will still be accepted. This option is configured in the OnTheClock settings under the “Enforcement Type” for IP restrictions.

2. Steps to change this in OnTheClock:
- Log in to OnTheClock as an admin.
- Go to Settings > Time Clock Settings.
- Find the Punch Site or IP Restrictions section.
- Change the enforcement from a single IP to a multi-IP range or expand the allowed IPs.
- Save changes.

3. Consider Network Setup: If possible, ask your network admin or ISP about getting a static IP or a reserved DHCP IP on your local network to prevent IP changes on your device.

4. Alternative: If changing IP enforcement is not viable, consider clocking in using a method not reliant on IP restrictions, like GPS or device-based restrictions, if your plan allows it.

Would you like me to guide you step-by-step through adjusting the IP restrictions in your OnTheClock admin portal? Or do you want tips on checking your network for a static IP setup?

This info about multi-IP range allowance is from OnTheClock’s help section here:
Location and Security Restriction Setup - OnTheClock

Let me know how you want to proceed!

can you tell me if someone is trying to clock in from their phone, would this change the IP

Great question! Yes, if someone clocks in from their phone, their IP address could indeed change compared to when they are on a fixed office or home network.

Here’s why:

- When using mobile data (4G/5G), phones get assigned IP addresses from the cellular provider’s network, which often changes frequently.
- If the phone is on Wi-Fi, it will use the IP assigned by that Wi-Fi network’s router, which might be static or dynamic depending on the network.
- Because of this, an employee clocking in from their phone could have a different IP address every time, especially if they're switching between different Wi-Fi networks or mobile data.

So if your OnTheClock settings restrict clock-ins to specific IP addresses or ranges, a phone clock-in from a changing IP will be blocked unless the phone’s current IP is added or the restriction is broadened.

To avoid this, many use the “Multi IP Range” enforcement setting in OnTheClock, which allows clock-ins from a range of IPs or multiple IPs, accommodating changing addresses from mobile devices1.

If mobile access is important for your team, I recommend modifying that setting or using GPS/geofencing features to verify clock-ins instead of relying solely on IP restrictions.

Would you like help adjusting these restrictions in your OnTheClock admin settings?

No. I think I got it. problem is we are not allowed to clock in Mobily. So I think I can fix it

Glad to hear you're on the right track! Since you don’t allow clock-ins via mobile, OnTheClock has specific features to help you enforce that restriction effectively.

Here’s how you can set mobile clock-in restrictions:

1. Navigate as Admin: Log in to OnTheClock with your admin account.
2. Employee Profiles: Go to Employees, select the specific employee(s) you want to restrict mobile clock-in for.
3. Location or Device Restrictions: Within the employee profile, look for settings related to Punch Locations and Devices or Clock-In Methods.
4. Disable Mobile Clock-In: You can restrict the clock-in method to only allow desktop or specific approved devices, blocking mobile phone clock-ins altogether.
5. Save Changes: Make sure to save the updates to enforce these restrictions.

This approach prevents employees from clocking in from their phones and will reduce the IP mismatch issues you’re experiencing from mobile device IP changes. It matches your policy of disallowing mobile clock-ins while securing the process1.

If you want, I can walk you through the exact clicks and settings inside the admin portal to set this up fully. Would you like that?