Access control systems and hardware¶
Select Controller under Physical Access Control Settings to review the site's access-control systems. The inventory includes the controller name, post, system and controller types, MAC address, serial number, pending updates, health notification address, online status, and last-seen time.
Search filters the controller inventory. Visualize Hardware opens a site-level hardware diagram, and Refresh reloads controller state.
Add or edit a controller¶
Select Add New, or use a row's action menu and select Edit. Every controller requires a name and System Type. Azure also requires a Controller Type. Port, when shown, must be numeric.
Fields change with System Type:
| System type | Type-specific fields and actions |
|---|---|
| Azure | Controller type, MAC address, serial number, external ID, Hardware Setup, Utilities, Send Configuration, and Erase Configuration. |
| VertX | Host address, MAC address, serial number, external ID, interfaces, and Utilities. |
| Keri | MAC address, serial number, external ID, interfaces, and Reboot Controller for a saved record. |
| DSX | DSX UID field, UID field number, and company values, plus interfaces. |
| Axis | IP address, port, username, and password, plus interfaces. |
| Other supported types | General controller identity, post, health-alert, and notes fields; interfaces are available when the type is not Azure. |
You can associate the controller with a site post and enable health alerts with email and phone destinations. Last-seen status and last-modified information are displayed in the site's configured time zone.
Warning
Changing System Type clears values that do not belong to the newly selected type when you save. Capture the existing integration values before changing type.
Azure controller type changes¶
Creating an Azure controller automatically applies the default hardware definition for the chosen controller type. Changing an existing Azure controller between supported 2-door and 4-door types displays a confirmation because saving resets its existing hardware configuration and reapplies matching defaults.
Cancel the confirmation if you have not documented the existing ports, readers, access points, inputs, outputs, and strike wiring.
Row actions¶
Depending on controller type and permission, the action menu can include:
- Edit and Change History;
- Health Details when a health target exists;
- Interface for non-Azure integrations;
- Utilities for Azure and VertX controllers;
- Hardware Setup, Send Configuration, and Erase Configuration for Azure;
- Delete for users with modify permission.
Azure Hardware Setup is the authoritative portal definition for its serial ports, peripherals, readers, access points, inputs, outputs, and strikes. See the Field Technician hardware guide for hardware-level procedures and safeguards.
Interfaces and legacy hardware¶
An interface belongs to a controller and supplies the panel-level identity used by legacy integrations. Configure its controller, name, serial number, coordinates, and panel address before assigning readers. Only active interfaces and controllers are offered in downstream selectors.
Deleting an interface or reader presents a dependency-impact message and performs a hard cleanup of the related records. Read the entire impact message before confirming.
Synchronization and physical verification¶
Send Configuration, Utilities, schedule/reader/access-group sync, and credential delivery are separate operations. Use the controller's Pending Updates badge or open Configuration queue to inspect queued work. Then verify controller health and test the physical opening.
Erase Configuration and Keri reboot affect live hardware. Use them only under an approved maintenance procedure with a recovery path.