Understand an access control integration
Work through credentials, readers, controllers and door state, including how access decisions reach the equipment.
Sources and scopeRead before use
Navigation or project guidance; not a claim of product, standards or environment validation.
On this page
1. Learn the system roles#
Read PACS architecture and panels, readers and door I/O. Identify the authoritative controller and what it can decide while the server is offline.
2. Separate credential and reader link#
Read credentials, OSDP and legacy reader interfaces. Keep the credential proof, reader transport and access policy separate.
Next useful check: does the configuration actually use the security mode the design assumes?
3. Follow lifecycle changes#
Read credential lifecycle, offline operation and the relevant access platform API.
Track a revocation from the source account through to the enforcement point. A successful API update is only one stage.
4. Keep physical safety outside guesswork#
Read locks, egress and life safety and the safety impact checklist.
This route does not authorise wiring, door control or live acceptance testing. Those belong to the approved site process and qualified people.
Practise offline#
Use the reader message exercise with synthetic data. Keep interpretation separate from authentication and from the right to operate a door.