Office access alerts
Office access alerts: which events need a response?
An access event becomes useful as an alert when someone knows what to do with it. Start with the response the building needs, then configure the trigger and recipient.
Enlarge photo The decision
Separate records from interruptions
An office access alert brings a configured door, credential or device condition to the attention of designated staff. Routine access events belong in the activity record. Alerts should draw attention to conditions that require review or intervention. Their priority depends on the entrance and context: a disconnected reader at a storage room and one at the only staffed entrance can have different consequences.
Verify what the system can detect
A door-held condition generally needs a reliable position signal and an agreed time threshold. A forced-door condition needs the system to distinguish an unexpected opening from a permitted exit or release. These depend on sensors, wiring and configuration.
Ask the installer to demonstrate each proposed alert at the actual door. Include request-to-exit devices and legitimate scheduled openings so normal use is not repeatedly reported as an incident.
On a narrow screen, scroll the table horizontally to see every column.
| Condition | Input to verify | Response to assign |
|---|---|---|
| Door held open | Position signal and agreed delay | Check expected activity, then follow the site response plan |
| Unexpected opening | Position, authorization and exit signals | Review the context and escalate according to site procedure |
| Device disconnected | Communication monitoring and detection delay | Check affected entrances and activate the agreed assistance route |
Set thresholds around real use
Allow enough time for expected activity such as deliveries or accessible entry, while keeping prolonged openings visible. Review repeated access refusals with their reasons: an expired contractor credential and an unknown credential call for different responses.
Record why each threshold was selected. Adjust it after observing normal operation, rather than disabling an alert because it generates too many notifications during the first week.
Assign an owner and an escalation path
For each alert, name the first recipient, coverage hours, backup contact and action to take. Define when a remote review is sufficient and when someone must attend the site.
Lexoh’s configured event and device views can support that review. Confirm the available notification methods and permissions during the project; do not assume every event type is delivered through every channel.
Test disconnects and recovery
A platform can detect that a device has stopped communicating, while events generated at that device may be unavailable until connectivity returns. Confirm the detection delay, local storage and recovery behaviour for the selected configuration.
Review unresolved alerts and repeated causes on a regular schedule. Useful measures include actionable alerts, time to acknowledgement and recurring equipment faults. A larger notification count is not evidence of better security.
Questions
Practical questions
Does acknowledging an alert resolve the door condition?
No. Acknowledgement records that someone has taken notice, where that function is configured. The team must still verify the physical condition or device fault and record the outcome through the agreed process.
Are text messages and round-the-clock monitoring included?
Notification channels, recipients, delivery conditions and staffed response are separate scope items. Confirm the available methods, coverage hours and fallback with Lexoh; a notification setting alone does not provide an operator to respond.
Should every refused credential create an urgent alert?
No. Assess the reason, repetition and entrance involved. Routine mistakes can usually be reviewed without interrupting the whole team.
Can alerts continue during a network outage?
The platform may report a disconnection, but it may not receive new events from that device. Verify the exact behaviour and recovery process.
References and further reading
- Office access control
Lexoh product or project reference.
- Cloud platform
Lexoh product or project reference.
- Building access control
Your project
Build an alert response plan
Review the doors, available signals and team coverage with Lexoh before selecting alert rules.
Discuss the project