# Secure Access Control Areas with Anti-Passback

The Verkada anti-passback feature allows you to increase the security of an area by ensuring that each user enters the area and then exits the area before they can enter again. Using anti-passback, you can prevent users from entering an area and then passing their badge back to someone else to use to enter the same area. Additionally, anti-passback can help enforce a badge-out policy, whereby users must badge when the exit an area or else they will violate anti-passback when they try to re-enter.

Anti-passback rules are based on the configuration of an access control area. An access control area is configured for a site, and is defined by a set of entrance doors and exit doors. Learn more about how to [configure an access control area](https://help.verkada.com/access-control/configuration-and-setup/configure-access-control-areas).

{% hint style="warning" %}
In Canada, anti-passback and areas are only supported on the AC12.
{% endhint %}

## Double entrance and double exit violations

Anti-passback works by monitoring whether a user is properly exiting an area that they have entered, before they attempt to enter again. Similarly, it monitors whether a user is properly entering an area they have exited, before they attempt to exit again. In other words, anti-passback looks for violations when a user attempts to enter an area twice in a row, or exit an area twice in a row.

If a user has access granted to an entrance door, and then badges at an entrance door again without having access granted to an exit door in between, they will receive a **double entrance violation**.

Similarly, when a user has access granted to an exit door, and then badges at an exit door again without having access granted to an entrance door in between, they will receive a **double exit violation**.

## Types of anti-passback

Verkada access control supports hard anti-passback and soft anti-passback:

**Soft Anti-Passback**

A user who receives a violation maintains their normal access to entrances and exits of the area, even before the violation is cleared.

**Hard Anti-Passback**

A user who receives a violation is denied access at all entrances and exits of the area until the violation is cleared.

{% hint style="danger" %}
Carefully consider the consequences when you enable **hard anti-passback**. The hard anti-passback rules can result in users unknowingly having anti-passback violations and being denied access.

Carefully consider the configuration of your area’s entrances and exits, and properly communicate the intended badging policy to users before turning on hard anti-passback. If a user is in violation, that violation can only be cleared by an Access Site Admin or Access Site Manager of the site. Learn more about [Roles and Permissions for Access Control](https://help.verkada.com/access-control/roles-and-permissions-for-access-control).

Verkada’s support team is unable to grant access to or clear the violation of a user who is in anti-passback violation.
{% endhint %}

## Set up anti-passback for an access control area

{% hint style="danger" %}
Before you can set up anti-passback rules, you must [configure an access control area](https://help.verkada.com/access-control/configuration-and-setup/configure-access-control-areas).
{% endhint %}

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Access**.

{% endstep %}

{% step %}

#### Select a site from the **All Sites** dropdown.

{% endstep %}

{% step %}

#### At the top, click **Area**.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-e49cdd24f011fa43824b87a6aabf81e6d1dfc3bf%2F394e37384a68cf6aa7a4c62b634a5827f5a9af57.png?alt=media" alt="" width="675"></div>
{% endstep %}

{% step %}

#### At the top of the area details page, click **Area Settings** to see the current area configuration. To update the configuration, click the gear icon and follow the steps.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-a7f4ae05a80b6d3fa3b9f33cdf58855954ddbb88%2Fa9f72e3a727c0b176cfd1d027e7afb6b187dd951.png?alt=media" alt="" width="1469"></div>
{% endstep %}

{% step %}

#### Select **hard anti-passback** or **soft anti-passback**.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-ed87e94ddcd9abe02e2b3082e7fc47cebe593437%2Fd614352acc06511c34e9b562105495a9325a8790.png?alt=media" alt="" width="308"></div>
{% endstep %}

{% step %}

#### Designate any access groups that you want to be exempt from anti-passback rules for this area.

{% endstep %}
{% endstepper %}

{% hint style="info" %}
Carefully consider which access groups should be anti-passback **Exempt Groups**. We recommend that you add security personnel, and anyone who needs unimpeded access at all times, as an exempt group.
{% endhint %}

## Manage anti-passback violations

To manage anti-passback violations, use the area details page (see instructions above). There, you can navigate to the **People in Violation** tab to see who currently has an anti-passback violation.

### Review anti-passback violations

To review an anti-passback violation, click a user in violation to open the violation timeline review page. On this page, you can examine the events leading up to and following the violation.

### Clear anti-passback violations

You can clear an anti-passback violation from the **People in Violation** tab, or from the violation timeline review page.

## Set up alerts for anti-passback violations

You can set up alerts that will trigger notifications for anti-passback violation events. To do this, follow these directions to [set up an access control alert](https://help.verkada.com/access-control/alerts-and-events/configure-access-control-event-alerts), and configure the alert for anti-passback violations.

## Essential safety practices

{% hint style="danger" %}
When you select hard anti-passback, your area **must** allow free egress in the case of an emergency.
{% endhint %}

Hard anti-passback results in a user who is in violation having access rejected at all entrances and exits of the area. Therefore, for safety purposes, it is **essential** that such user is able to safely exit the area in the case of an emergency.

### Free emergency egress

Free emergency egress can be achieved in a variety of ways, such as:

* Mechanical egress via a crash bar or handle
* Break-glass request-to-exit (REX) that drops power to a maglock

You can configure Verkada access control to produce a door forced open (DFO) event when the emergency egress is used rather than properly badging at the exit. This DFO event can be optionally configured to trigger an AUX out signal, which can be connected to a strobe or siren. In this way, you can disincentivize use of the emergency egress mechanism in non-emergency scenarios.

{% hint style="danger" %}
Free emergency egress **must** be enabled via a system that is independent of fire alarm pull stations. See below for example access control free emergency egress devices.
{% endhint %}

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-cf55fd56755ba7546e3e3f4c51995021ec714e1b%2F707bb94e6a5b2f1b099793b6f9be388e97255c02.png?alt=media)

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=eFp7akwYJek).
{% endhint %}

{% hint style="success" %}
**Need more help?** Contact [Verkada Support](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/need-help/contact-verkada-support).
{% endhint %}
