Skip to content

Known limitations

This page lists first-release behavior that’s worth knowing about explicitly, rather than leaving it implied by silence elsewhere in these docs.

Reporting-timezone changes can affect historical totals

Section titled “Reporting-timezone changes can affect historical totals”

Each session records which reporting timezone was in effect when it started. Today, daily totals are calculated using the organization’s current reporting timezone setting, rather than each session’s recorded timezone. In practice, this means that changing an organization’s reporting timezone can shift where midnight falls for already-closed historical sessions, affecting their day-boundary totals retroactively. If your organization’s reporting timezone is stable, this doesn’t come up in practice — it matters specifically around a timezone change.

No distinct record of why a location is missing

Section titled “No distinct record of why a location is missing”

At clock-in and clock-out, a missing location on an event doesn’t currently distinguish between “the employee denied the location permission,” “location capture failed,” and “location wasn’t requested for that event.” All three look the same: an event with no location attached.

Late-correction deadlines are informational only

Section titled “Late-correction deadlines are informational only”

A correction request can be marked with a late flag and a reason, but there’s currently no automatic enforcement of an organization’s correction-deadline policy — the flag records that a request was late; it doesn’t by itself block or bound how late a request can be.

Privilege changes don’t require a fresh sign-in

Section titled “Privilege changes don’t require a fresh sign-in”

Changes to an account’s privileges (for example, granting or removing administrator access) are recorded with an audit entry and protect against removing the last active administrator, but they don’t currently require the person making the change to have signed in recently — there’s no additional re-authentication step at the moment of the change.


None of these affect the core guarantees around evidence integrity: originals are always preserved, nothing is auto-merged or silently discarded, and official totals only ever include closed, confirmed, or explicitly approved time.