AllBox activity logs¶
Activity Logs is the site-scoped operational event history produced by AllBox workflows. Use it to trace calls, directory activity, pass validation, gate-open events, printing, device connectivity, and related identifiers.
In General Administration, select a specific site and then select Activity Logs. A site must be selected before the dialog can open.
Note
This is not the administrative Audit History. Activity Logs describe AllBox behavior; Audit History describes changes to configuration and business records.
Start with the device filter¶
When the selected site has AllBoxes with device identifiers, the first AllBox is selected automatically. The initial results are therefore limited to that device.
- Keep the selection to investigate one AllBox.
- Clear the AllBox selection to include all device identifiers at the site.
- If an expected AllBox is absent, confirm its configuration has a device identifier.
The date range defaults to approximately the preceding 24 hours. Enter both a From and To value to apply a bounded date filter. If only one endpoint is present, the date restriction is not applied.
Filter activity¶
Use the available filters together:
| Filter | Behavior |
|---|---|
| AllBox | Matches the selected device identifier. |
| Activity Type | Matches one defined AllBox event type. |
| Search | Searches the event description only. |
| From / To | Includes records between both entered date-time values. |
Activity types include call-center initiation, answer, timeout, connection error, local hangup and completion; directory and video calls; concierge calls; gate opens; member PIN and ID-card activity; visitor-pass success or failure; pass printing; temperature alerts; general messages; and device online or offline events.
Select Apply after changing popover date filters. The main AllBox, activity-type, and search filters refresh as they change. Use Refresh to retrieve newly arrived activity.
Read and correlate rows¶
| Column | Use |
|---|---|
| Created Date | Event time displayed in the selected site's configured time zone. |
| Description | Human-readable activity or a recording link. |
| Unique Id | Identifier for this event, call, or workflow item. |
| Parent Unique Id | Identifier connecting the item to a parent call, session, or workflow. |
Sort the grid by Created Date, Description, Unique Id, or Parent Unique Id. For a sequence investigation, sort Created Date explicitly and compare related identifiers instead of relying on the grid's initial row order.
Descriptions containing a recording link are displayed as Recording Link and open in a new browser tab. Access may depend on provider authorization, link lifetime, network policy, and recording-retention settings. Treat recordings and their URLs as sensitive information.
Common investigations¶
A visitor could not enter¶
Filter to the AllBox and incident window, then look for pass failure or success, call activity, gate-open activity, and connection errors. A successful pass or gate-open log means the workflow recorded the action; it does not prove that the physical gate moved. Correlate it with access transactions, controller health, relay configuration, and onsite observation.
A call failed or ended unexpectedly¶
Follow the Unique Id and Parent Unique Id across initiation, sent, answer, timeout, error, hangup, and completion events. Review the recording link when authorized, then compare the timestamps with telephony-provider and AllBox health records.
A device went offline¶
Filter to Device Offline and Device Online activity for the AllBox, then compare the interval with Health Monitor, network or power events, and the target's component history.
Activity Logs cannot edit, delete, replay, or annotate an event. Preserve the identifiers and timestamps when escalating an issue.