Access Control

Access-control hardware - doors, locks, and card readers - is modelled in the app as a door assembly: a parent door that groups its child peripherals. This page explains how those assemblies are presented and operated.

How a door is structured

A door brings together its child sensors:

Locks - the operable lock points on the door.
Readers - the card or credential readers, including their position.
Presence and buttons - supporting sensors used for entry and exit.

The app understands several controller hardware variants and assembles the correct child sensors for each. In the door’s detail view, doors, locks, and readers are separated so you can select and inspect each one. See Sensor detail views.

Operating a lock

From a lock’s detail view you can operate the lock with a toggle - where you have the access rights for it. Locks you aren’t permitted to operate are shown but can’t be actuated.

Tip: Searching for a door in any list also matches the relevant lock within the door assembly, so you can find a specific lock by the door’s name.

How alarm state is judged

A door is considered in alarm if a relevant child sensor is in alarm. To keep this accurate and quiet, the app:

Accounts for whether you have access to a given lock when judging its state.
Ignores non-meaningful child types (such as buttons and presence) so the door’s overall state reflects what matters.

Access events - entries, exits, and door activity - also appear on the Events & recordings timeline, where you can filter by the user involved.