The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page
How do I enable Anti-Passback and Occupancy Management?
Anti-Passback allows you to define a sequence in which entries must be accessed to gain entry. This sequence is managed using Areas, where each Area contains a set of inbound and outbound entries.
Steps to Set Up Anti-Passback
Navigate to Anti-Passback Settings:
Go to
Sites > Zones
.Click on the Zone you want to edit.
Click on the
Anti-Passback
tab in the upper right-hand corner.
Configure Anti-Passback Settings:
Expiration Time: Enter an expiration time after which the Anti-Passback state will reset for the user.
Periodic Reset: Enable
Reset Anti-Passback Periodically
to set a schedule where users are not restricted by Anti-Passback logic until their second unlock attempt. This also applies to Occupancy Limiting Mode.Contact Sensor: Enable
Use Contact Sensor
to change a user’s Anti-Passback state only after the Contact Sensor reports open.Shared Orgs Reset: Enable
Shared-To Orgs Can Reset Anti-Passback
to allow organizations sharing this Zone to reset Anti-Passback for their users.
Define Areas:
Add Area: Click
Add Area
to define a new Area within the Zone to be enforced by Anti-Passback.Name: Enter a name for the Area.
Modes: Set the Inbound Mode and Outbound Mode to determine the system's reaction to Anti-Passback breaches:
None: Access is granted without any additional response.
Alert: Access is granted and an event is generated.
Enforce: Access is denied and an event is generated.
Add Entries:
Inbound and Outbound Entries: Add entries for inbound and outbound access.
An entry can only be used once within an Area (either as Inbound or Outbound) but can be used in multiple Areas.
Entries may span multiple ACUs, but those ACUs must reside on the same LAN.
To limit occupancy, select only one Inbound Entry and one Outbound Entry.
Occupancy Limiting Mode: If limiting occupancy, select
Alert
orEnforce
from the Occupancy Limiting Mode dropdown, then enter the Occupancy Limit.Note: This option is only available with the Premium Package. If limiting occupancy, 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.
Save Changes:
Click
Save
to apply your configurations.
Important Notes
For each Area, after every successful inbound entry, the user must exit through an outbound entry before entering an inbound entry again. This prevents users from sharing credentials.
Anti-passback can also be used to limit occupancy, preventing users from accessing inbound entries until enough users have exited through outbound entries.
Additional Configuration
Alerts: To receive notifications of Anti-Passback and Occupancy Limit breaches, see "How do I set up alerts?"
Custom Rules: To configure custom rules around these events, see "Creating a rule with the Rules Engine"