User's Guide
ANTI-PASSBACK
Anti-Passback lets you define a sequence in which Entries must be accessed in order to gain Entry.
Sequences are defined using Areas –each Area contains a set of inbound and outbound Entries.
For each Area, after every successful inbound Entry the user must exit through an outbound Entry
before entering an inbound Entry again. This feature is commonly used with parking gates and
helps prevent users from sharing credentials with other users.
● To set up Anti-Passback on a Zone, click on the Zone to edit it, then click on the Anti-Passback
tab in the upper righthand corner.
● Enter an Expiration time in seconds after which the Anti-Passback state will reset for the user.
● Enable Reset Anti-Passback Periodically to configure a schedule during which a user is not
limited to Anti-Passback logic until after their second unlock attempt.
● Enable Use Contact Sensor to only change a user’s Anti-Passback state until after the Contact
Sensor reports open.
● Enable Shared-To Orgs Can Reset Anti-Passback if you want orgs sharing this Zone to have
permission to reset Anti-Passback for their users.
● Lastly, define the Area(s) within the Zone to be enforced by Anti-Passback.
○ Enter a name.
○ Set the Inbound Mode and Outbound Mode, which determines how the system reacts
to Anti-Passback breaches:
■ None – access is granted; no additional response
■ Alert – access is granted and an event is generated
■ Enforce – access is denied and an event is generated
○ Add Inbound and Outbound Entries.
■ Note: An Entry can only be used once within an Area, either as Inbound or
Outbound but not both; however an Entry
can
be used in multiple Areas. In
addition, all Entries within an Area must reside on the same ACU.
○ Click Add Area.
● Click Save.
Internally, the ACU tracks each user’s most recent direction of movement (inbound or outbound)
within each Area. When the user’s most recent direction is known, then an attempt by that user to
move in the same direction again will result in an Anti-Passback Breach event. When the user’s
most recent direction is unknown, as in the case of a newly created Area, or following a scheduled
or manual Reset action, then the user’s next movement will be allowed in either direction, after
which normal rules will apply again.
Anti-Passback Breach events can trigger alerts. See ALERT SETTINGS. They can also be used to
trigger custom integrations. See OUTBOUND WEBHOOKS.
Version 1.9
©
Openpath 2019
Page 20