Why does Zoho People geolocation check-in fail even with location allowed?

Geolocation check-in in Zoho People can fail even when location is allowed if the device reports an inaccurate location, the user is outside the allowed geofence radius, precise location is off on the phone, a VPN or desktop browser gives a wrong position, or IP restrictions also apply. Check the attendance settings, the geofence, and the device's location accuracy first.

Zoho People can restrict check-in by location, IP address or both. If both are set, a correct location still fails on the wrong network. Admins should check the attendance settings for the user's location group and confirm which restrictions apply. Geofence radius is another common issue: a tight radius around an office can reject staff standing in the car park or on another floor.

Devices vary in accuracy. Desktop browsers often locate by IP or Wi-Fi, which can be far off. On phones, the app needs precise location, not approximate, and battery saving modes can delay a fix. VPNs can make the location look like another city. Ask the user to open a map app first, wait for a precise fix, then check in.

For field staff, consider check-in through the mobile app only, with a sensible radius for each site. Keep a simple process for managers to approve regularisation requests when check-in fails, so attendance is not lost. Check the current Zoho People help for options on your edition.

Written by Flowpeak, a Zoho implementation partner. Zoho pricing and features change, so confirm current details on the official Zoho site. Free checklists | Ask us a question