Bottom line: a direct relay or door-output command can bypass the access-control application’s expected state. That capability should not become a convenient operator shortcut because monitoring, schedules, credentials, and audit meaning may no longer match the physical lock.
\nThe AXIS A1610 Network Door Controller User Manual — Door override warns that direct control of a relay used for a door can override relay configuration in AXIS Camera Station. The manual directs use only when instructed by Axis support and says to stop Secure Entry before that direct-control procedure.
\nThe warning identifies a support boundary: normal PACS commands and low-level output control are not interchangeable. A physical result achieved outside the normal application can leave operators with an inaccurate or incomplete understanding of door state.
\nThe manual applies to the specific controller and documented software context. It does not authorize a general bypass, define an emergency-access policy, or replace fire, egress, accessibility, electrical, or lock requirements. Other products may have different controls and restoration steps. Only qualified authorized personnel should act under current vendor support and site procedures.
\nThe following steps are DSE recommendations based on the cited source.
\nRestrict the capability to trained administrators and do not publish low-level steps in general operator instructions. Require incident or change identifier, affected door, observed fault, support case and instruction, safety review, approver, two-person confirmation, alternate guard or mechanical control where needed, start time, and maximum duration. Preserve required egress and coordinate with fire/life-safety responsibility before any action.
\nAfter vendor-directed work, restore the supported application state and independently test authorized access, denial, relock, door contact, forced and held alarms, schedule, event delivery, and audit logging. Revoke temporary privilege and reconcile every access during the exception window.
\nRetain the support case, approved procedure, exact model and versions, authorization, personnel record, alternate-control log, start and end times, sanitized configuration evidence, restoration test, access-event reconciliation, privilege review, and incident closure. Never include credentials or exploitable bypass detail in broadly distributed evidence.
\n