Access Logs
The Access Logs tab is the audit trail: every unlock attempt — successful, denied, or failed; from the mobile app or by an admin — is recorded with who, which door, when, where from, and the outcome. This page covers reading the log, filtering, exporting to CSV, and the event detail view.
Figure 1: The Access Logs tab
Events are retained for approximately 13 months, then removed automatically. Deleting a user does not delete their events — history is kept for the audit trail.
Filtering and searching
Figure 2: Search, time window, and state filter
| Control | Options |
|---|---|
| Search | "Search door, user, event ID…" — matches door name/ID, user name/ID, event ID, command ID, state, and denial reason |
| Time window | Last day, Last 7 days (default), Last 30 days, Last 90 days |
| State filter | All states, Confirmed unlocked, Denied, Timed out, Failed |
The header shows the event count for the current window and filters. Each window loads up to the 500 most recent events.
Event states
| State chip | Meaning |
|---|---|
| Confirmed unlocked | The door controller confirmed the relay released — the door actually unlocked |
| Unlocked | The unlock was reported successful |
| Admin Unlocked | An admin triggered the unlock from Performance Hub (admin override). Recorded as soon as the command is dispatched |
| Denied | The request was rejected — see the Reason column (all reasons) |
| Pending / Request received | The request is still being processed (transient — normally resolves within seconds) |
| Timed out | The unlock command was sent but the controller didn't confirm in time — usually connectivity trouble at the door |
| Failed | The unlock could not be completed due to an error |
Each row shows the timestamp, state, door, user, distance from the door and command latency (when available), and the denial reason for denied events.
Event details
Click any row to open the Access Details dialog.
Figure 3: The Access Details dialog
The header shows the door, its location, the outcome, an Admin override badge when applicable, and the denial reason if denied. Fields shown when available:
| Field | Notes |
|---|---|
| Date / Time | When the attempt happened |
| Coordinates | The location the phone reported, with GPS accuracy (±N m); copyable |
| Door / Gate | Door name and location |
| User or Admin | Who attempted — admin unlocks show the admin's account |
| Device | The phone/device used |
| IP Address | The requesting IP; copyable |
| Hold time | How long the door stayed unlocked |
| Distance from door | Computed distance from the geofence centre |
| Event ID / Command ID | Copyable identifiers for support escalation |
Unlock Location plots the reported coordinates on a map with an Open in Google Maps link. When there are no coordinates you'll see "No location captured — unlocked from the Performance Hub." (admin overrides) or "No location data was reported for this unlock attempt."
Exporting to CSV
Click Export CSV to download the currently filtered events. The file contains: timestamp, state, door ID, user ID, person ID, denial reason, distance (metres), and latency (ms). The button is disabled when the filtered list is empty.
Tips
- The Doors tab's Recent activity card is a 24-hour shortcut into this log — clicking an event there jumps straight to it here.
- Investigating a member complaint? Filter to Denied, search their name, and read the reason — then see Troubleshooting for the fix per reason.
- A burst of Timed out events on one door usually means that door's controller has network problems — check its status in the Doors tab.
Related pages
- Reference — every state and denial reason
- Troubleshooting
- Doors