Skip to main content

Set up location tracking and geolocation

For: Admins, HR Admins — Activate location tracking and geolocation: set up locations with a radius, warn or block check-ins from outside, and view location status.

Written by Thorsten Bannes

Activate location tracking

As an admin, you activate this feature per attendance policy in the settings.

  1. Go to Attendance > Settings > Attendance policies.

  2. Select a policy and click the three-dot menu.

  3. Select Edit policy.

  4. Go to Location tracking.

  5. Enable Allow location tracking by ticking the checkbox on the right.

  6. Decide si usar el comportamiento de seguimiento de ubicación solo para entrada, salida o ambas.

  7. Use Set geofence behavior to define what happens when an employee checks in outside a defined location:

    • Warn employee: The employee receives a notification but can still clock in from outside the location.

    • Block employee: The employee cannot clock in or out outside a defined location.

  8. Click Save changes.


Add locations

You must create one or more locations so your employees can track their location — for example, when they arrive at the office. For each location, you can set a valid radius.

  1. Go to Attendance > Settings > Locations (Geolocations).

  2. Click (+) Add location.

  3. Fill in the address details:

    • Name (required): Name of the location, e.g. Berlin Office

    • Address (required): Street and house number

    • City (required)

    • Country (required)

    • Postal code (required)

    • Radius (required): Radius around the location — available options are 0.1 km, 0.5 km and 1 km

  4. Click Validate address.

  5. Click Save.


Edit locations

  1. Go to Attendance > Settings > Locations (Geolocations).

  2. Click the three-dot menu next to the location you want to edit.

  3. Click Edit and make your changes.


Delete locations

  1. Go to Attendance > Settings > Locations (Geolocations).

  2. Click the three-dot menu next to the location you want to delete.

  3. Click Delete.

Good to know:

  • If location tracking is disabled or no locations are set up, time tracking works as usual.

  • If an employee has not enabled location tracking on their phone, time is recorded without a location.

  • Location tracking only works on a mobile device, not in the desktop app.


Location tracking from the employee's perspective

Once location tracking is active, your employees can see whether they are inside or outside a defined location when they clock in and out.

Note: If an employee has disabled location tracking in their device settings, the location will not be captured and the time entry will be marked with a grey location icon.

Option: Warn employee

The employee receives a notification on their mobile device about whether they are inside or outside the location when clocking in — but they can still clock in.

Option: Block employee

The employee cannot use the clock in/out slider as long as they are outside a defined location.


View the location status of all time entries

In the Attendance summary, you can see as an admin, using a colour code, whether employees clocked in and out from inside the radius, outside the radius, or without a location.

Colors:

  • Yellow: The attendance was recorded at none of the saved locations.

  • Grey: The employee did not use GPS when recording.

  • Green: The employee recorded their attendance from a valid location.

Via Employee profile > Attendance you can also see where the person was when they recorded their time.


Frequently asked questions

Why is no location recorded for an employee?

No location is recorded for an employee either because location tracking is disabled on their device, or because they are clocking in via the desktop app. Location tracking only works on mobile devices.

What do the colours in the Attendance summary mean?

Green: recorded from a valid location.

Yellow: outside all saved locations.

Grey: location recorded without GPS.

Can I prevent employees from clocking in from outside?

Yes. Under the geofence behavior settings, select the Block employee option. This prevents clocking in and out outside a defined location.

Is the employee's location transmitted in real time, or only captured at the moment of clocking in?

Only at the moment of clocking. Location is captured as a one-off reading each time an employee clocks in, clocks out, or starts or stops a break. There is no continuous background tracking. On mobile, the app only requests location while in use, and only when the attendance policy has geolocation enabled.

What location data is specifically collected and processed?

For each clock event: GPS coordinates (latitude and longitude), accuracy in metres, and a human-readable address. Kenjo also computes whether the reading was within the allowed radius, the distance to the target location, and the target location's name and address. No continuous location history is kept — only the point tied to each attendance entry.

How long is this data stored?

Location data is part of the attendance record and follows the same lifecycle as all other customer HR data. There is no separate or configurable retention period for location data alone. After contract end there is a 30-day transition period, after which remaining customer data is deleted. A CTO-signed deletion certificate can be provided on request.

For what purposes is location data processed?

Solely for attendance verification (geofencing): Kenjo checks whether the employee is at a valid, defined work location when clocking in or out, and can optionally raise an alert when clocking occurs outside the allowed area.

Who can access the location data?

Inside the app, the data is visible to users with the relevant attendance permissions (for example, in the employee's day view, audit log, and the Who's-checked-in view, all permission-gated), as well as to the employee themselves. On Kenjo's side, production data access is restricted to authorised staff via VPN and MFA. All access to a customer instance is logged.

What technical and organisational measures are in place to protect this data?

Data is encrypted at rest (AES-256) and in transit (TLS), stored in the EU (Frankfurt, MongoDB Atlas; documents in S3 eu-central-1). Access is governed by role-based access control, mandatory MFA, and VPN, with least-privilege principles, annual access reviews, and audit logging. Full detail is in the Compliance and Cybersecurity FAQ and the Data Processing Agreement (DPA, Annex 2 for subprocessors).

Did this answer your question?