Bottom line: anti-passback is a state machine, not a reader checkbox. If the system misses an exit, accepts a door state incorrectly, or loses coordination across controllers, a valid user can be denied and the occupancy record can become unreliable.
\nThe AXIS Camera Station Secure Entry User Manual documents anti-passback modes and configuration. It states that doors participating in anti-passback need door-position sensors. It describes hard, soft, and timed behavior and explains that some offline operation depends on the relevant doors being connected to the same controller. The manual also places conditions on a zero timeout, including reader coverage on both sides.
\nThese dependencies mean a logical area must match the physical route. An unmonitored emergency exit, propped door, elevator, gate, or door on another controller can change a person’s actual location without producing the transition that the anti-passback state expects.
\nThe manual applies to compatible Axis products and documented versions. It does not establish that anti-passback is suitable for a life-safety, labor, occupancy, privacy, or high-security requirement. The feature does not prevent tailgating by itself and should not be treated as an authoritative people count. Fire and emergency egress must remain compliant.
\nThe following steps are DSE recommendations based on the cited source.
\nDraw the zone with readers, sensors, controllers, doors, gates, stairs, elevators, emergency exits, and alternate routes. Test correct entry and exit, repeated entry, repeated exit, tailgating observation, held and forced door, missed sensor transition, credential use at two points, controller offline state, server loss, and reconnection. Use test identities and an approved window so no person is trapped or denied required egress.
\nDefine hard, soft, or timed handling from the operational consequence. Create a least-privilege reset procedure that records identity, old state, corrected state, reason, approver, operator, and related incident. Reconcile state after evacuation or a broad emergency release.
\nRetain the zone drawing, version and controller topology, sensor tests, configuration export, sequence matrix, access and violation events, offline and recovery results, reset audit, emergency reconciliation procedure, and acceptance signatures. Re-test after route, reader, sensor, controller, timeout, or software changes.
\n