Tamper protection
What is this view for? Here you define, per property, how LiteLog verifies that actions really happened on site — the location verification. Without verification, a clock-in, incident, or task could in theory be submitted from anywhere; with verification, the app blocks actions that do not happen on site.
Navigation (portal): Master data → Properties → select a property → panel entry "Tamper protection" (group "Administration")
Navigation (LiteLog app): Administration → Property settings → "Tamper protection"
The three areas
The page bundles verification for three feature areas. For each area you pick one method:
| Area | When is it checked? | Available methods |
|---|---|---|
| Time tracking | When clocking in and out | Off · Geofencing (GPS) · Beacon |
| Incidents & Forms | When submitting an incident or form | Off · Geofencing (GPS) |
| Tasks & Tours | When booking checkpoints and completing tasks | Off · Geofencing (GPS) |
The same selection is also available directly on the respective module pages (time tracking → proof section, incident settings, tour settings) — both places control the same setting.
The methods in detail
Off
No location check. Actions are possible from anywhere.
Geofencing (GPS)
When the action is completed, the app checks whether the device is inside the property's location area (the shape from the map assistant, with a tolerance buffer against GPS drift). Outside the area — or when no location can be determined — the action is blocked and the app shows a notice.
:::caution Prerequisite Geofencing needs a drawn property area and the app's location permission. Without an area, the check blocks with "location unknown". :::
Beacon (time tracking only)
Clocking in/out is only possible near one of the property's location verification beacons — ideal for fixed clock-in spots indoors (entrance, basement, underground garage) where GPS is unreliable. The server additionally validates the proof and stamps a trust level on every booking.
You bind beacons in the LiteLog app: Administration → Connect beacons → "Location verification". The same beacon also greets arriving staff with a clock-in hint and switches the active property automatically.
What about tours with beacons?
There is deliberately no separate beacon verification for tours: bind the checkpoints themselves as beacons instead. Every booking then physically happens at the beacon — automatically verified at the point, with no extra setting. NFC chips and QR codes achieve the same because they can only be scanned right at the point; this page's GPS geofencing complements both at the property level.
Good to know
- The setting applies per property and is off by default — existing properties do not change behavior until you actively choose.
- Blocked actions show the employee a clear notice ("Outside the property" or "Beacon out of range") — nothing is lost; the action can be repeated on site.
- If Bluetooth is unavailable on the device, the beacon check never locks anyone out; the booking is instead flagged server-side as "without proof" and stays auditable.