Note:AnentrycanonlybeusedoncewithinanArea,eitherasInboundorOutboundbutnot
both;howeveranentrycanbeusedinmultipleAreas.Inaddition,allentrieswithinanArea
mustresideonthesameACU,andallentriesbelongingtotheparentzonemustresideonthe
sameACU.
d. Iflimitingoccupancy,selecteitherAlertorEnforce(definitionsabove)fromtheOccupancy
LimitingModedropdown,thenentertheOccupancyLimit.
Internally,theACUtrackseachuser'smostrecentdirectionofmovement(inboundoroutbound)withineach
Area.Whentheuser'smostrecentdirectionisknown,thenanattemptbythatusertomoveinthesame
directionagainwillresultinanAnti-PassbackBreachevent.Whentheuser'smostrecentdirectionisunknown,
asinthecaseofanewlycreatedArea,orfollowingascheduledormanualResetaction,thentheuser'snext
movementwillbeallowedineitherdirection,afterwhichnormalruleswillapplyagain.
Anti-PassbackBreacheventscantriggeralerts.SeeAlertsonpage126.Theycanalsobeusedtotrigger
customintegrations.SeeRulesonpage124.
Note:Anti-passbacklogicalsoappliestoCloudKeycredentialsandotherremoteunlockmethods.In
general,youmightnotwanttoallowremoteunlockmethodsonzoneswithAnti-passbackenabled.
Resetanti-passbackonzonesandusers
Youcanresetanti-passbackonthezonelevelanduserlevel.
l
Toresetanti-passbackontheZonelevel,gotoZonesandclickResetAnti-passbackundertheAnti-
passbackAreascolumn.
l
Toresetanti-passbackonauserormultipleusers,seeIssueactionstousersonpage40.
Multipleareaanti-passback
Mostanti-passbackscenarioswillonlyrequireasingleArea,butmultipleAreascanbeusedtocreatemulti-
stepsequencesofentryaccess.Inthisexample,allfourReadersresideonthesameACUandareconfigured
acrossthreeAreas,resultinginacomplexflowofmovement.
Sites 54