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.
To set up Anti-Passback on a Zone, go to Sites > Zones, then click on the Zone to edit it, then click on the Anti-Passback tab in the upper right-hand corner.
Enter an Expiration time 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. This also applies to Occupancy Limiting Mode.
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:
1. None – access is granted; no additional response.
2. Alert – access is granted and an event is generated.
3. Enforce – access is denied and an event is generated.Add Inbound and Outbound Entries.
1. 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.
2. Entries may span multiple ACUs, but those ACUs must reside on the same LAN.
3. To limit occupancy, select only one Inbound Entry and one Outbound Entry.If limiting occupancy, select either Alert or Enforce (definitions above) from the Occupancy Limiting Mode dropdown, then enter the Occupancy Limit.
Note: This option only appears if you have the Premium Package. Also, if limiting occupancy, then all Entries within an Area must reside on the same ACU, and all Entries belonging to the parent Zone must reside on the same ACU.
11. Click Add Area.
12. Click Save.
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. You can also use Anti-Passback to limit occupancy and prevent users from accessing inbound entries until enough users exit through outbound entries.
To receive notifications of Anti-Passback and Occupancy Limit breaches, see How do I set up alerts? To configure custom rules around these events, see How do I use the Rules Engine?
0 Comments