The Web Time Clock in Microix Workflow Modules Modern allows users to clock in and out while recording their current location using Azure Maps. This feature helps administrators verify where employees are when recording their time entries.
However, users may notice that their recorded location does not always perfectly match their physical location. This is expected behavior and is influenced by the type of device and network connection being used at the time of clock-in.
When a user clocks in using the Web Time Clock, the system retrieves the current location from the device through Azure Maps. The precision of this location depends on how the device determines its position:
GPS-Based Devices (e.g., Smartphones or Tablets):
Use built-in GPS hardware for location tracking.
Provide high accuracy, often within a few meters.
Ideal for employees clocking in from the field or remote locations.
Wi-Fi-Based Devices (e.g., Laptops or Desktops):
Use IP address and Wi-Fi network triangulation to estimate location.
Accuracy varies depending on network quality and may show a general area instead of the exact spot.
The location may be offset by several hundred feet or more.
Using a corporate or shared Wi-Fi network: May return the network’s registered location, not the device’s.
VPN or remote access: Can route traffic through another city or state, causing inaccurate results.
Browser permissions: If location sharing is disabled or restricted, Azure Maps may fall back to a less precise method.
Device hardware limitations: Desktop computers without GPS sensors rely solely on network-based positioning.
Use a mobile device with GPS for the most precise location results.
Ensure location permissions are granted to the browser and the Microix web application.
Avoid using VPNs when clocking in if exact location data is important.
Location accuracy depends on the technology and network available to the user’s device.
Microix and Azure Maps cannot guarantee exact positional accuracy when users clock in via Wi-Fi or non-GPS devices.
Recorded locations should be interpreted as approximate when based on Wi-Fi or IP address detection.
For compliance or audit purposes requiring precise locations, users should clock in using a GPS-enabled device (such as a smartphone).
| Device Type | Connection Type | Expected Accuracy | Notes |
|---|---|---|---|
| iPhone / Android | GPS / Cellular | Within a few meters | Recommended for mobile staff |
| Laptop | Wi-Fi (Non-VPN) | Within 100–300 feet | May vary based on network setup |
| Desktop | Ethernet | City or regional level | Not recommended for precise tracking |