# Set Up an In/Out Door with Two Readers

An in/out door uses two consecutive door ports on an access controller:

* Door slot 1 (and sequentially any **odd numbered** port) is used for:
  * Door relay output
  * REX input(s)
  * DPI input
  * **Inbound access reader**, wired into the Wiegand or RS-485 reader inputs
* Door port 2 (and sequentially any **even numbered** port) is used for an **Outbound access reader**, wired into the Wiegand or RS-485 reader inputs:

<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-7cba948dfc60281715272943e1bae21ac3664104%2F3c5a273c6bc1fad582161ae342fd0b02c9eccbed.jpg?alt=media" alt="" width="563"></div>

Learn more about how to [wire a door to a Verkada access controller](https://help.verkada.com/access-control/installation/wire-a-door-to-a-verkada-access-controller).

***

## Set up an in/out door from Verkada Command

In/out door setup is very similar to a normal door setup, with two small differences:

* When you add the door to the access controller, select **In/Out Door** instead of **Door**.
* When you configure the in/out door, select two consecutive door ports on the access controller.

### Requirements

* Ensure that you have a Verkada access controller. This access controller **must** have two available reader slots for the in/out door that you set up.
* To avoid interference and ensure reliable reads when installing in/out readers:
  * Do not mount readers directly back-to-back on opposite sides of a surface thinner than \~200 mm (7.9 in).
  * If the surface is less than \~200 mm thick, vertically offset the readers by at least \~130 mm (5.1 in).
  * If the surface is thicker than \~200 mm, readers can be mounted directly back-to-back.

{% hint style="info" %}
**Recommendation**. You can use any two compatible readers of your choice, but we recommend two Verkada readers.
{% endhint %}

***

## Configuration

{% stepper %}
{% step %}
**In Command, go to the Devices page.**
{% endstep %}

{% step %}
**Select the access controller where you want to set up the in/out door.**
{% endstep %}

{% step %}
**Click Add.**

<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-54fd9ff9207dabc2f1e65e33db245a232cd48a93%2Fd93c67dec7139b13ea91e0b3a14068ce28a5b887.jpg?alt=media" alt="" width="1440"></div>
{% endstep %}

{% step %}
**In the Add Entity modal, select In/Out Door.**

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2FXJkFZbucpc5zknBbVnHc%2FScreenshot%202025-12-16%20at%203.38.15%E2%80%AFPM.png?alt=media&#x26;token=f3ccdca5-633f-4671-8122-c14b243eafdb" alt="" width="302"><figcaption></figcaption></figure></div>

The next screen allows you to populate a door name, building/floor, nearby camera, thumbnail, and set up the door slots for the Inbound and Outbound readers. The **Inbound Reader** is always the first slot, and the **Outbound Reader** is always the second slot.
{% endstep %}

{% step %}
**For Settings, type your values for each field and click Next.**

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2FfK4lHVmyHlfyHUoAUqVk%2FScreenshot%202025-12-16%20at%203.38.22%E2%80%AFPM.png?alt=media&#x26;token=08f70d59-0dd5-4380-ae56-f862f9dd8385" alt="" width="304"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Configure your Installer Setup settings and click Next.**
{% endstep %}

{% step %}
**Select your desired Access levels and click Done. On your access controller’s screen, you should now see the door setup similar to the example below. Note how there are 2 ports in the Port column of the table.**

<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-2b3a464c4bf06355fe45617ac466774177b5b9ac%2Fba430000105b1e8339b59eb0552955b1cfdecb16.png?alt=media" alt="" width="1377"></div>
{% endstep %}
{% endstepper %}

You can now continue to set up this door as if it was a normal door. If you apply a schedule to the door, the schedules carries over to both readers.

***

## Changes in the door events page

The *Inbound* and *Outbound* *Readers* can produce events that are tagged with the inbound or outbound direction. Access attempts, such as *Keycard Unlock/Keycard Denied*, now appear annotated with direction they are associated with (as shown below).

<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-48fa35ba379d3010180c1c293cfa451ec79c4896%2F601b24ef15ec7f9dfe83758548749a7348044756.png?alt=media" alt="" width="375"></div>

There is now an added filter on the door events page that allows users to choose to filter events based on the direction (Inbound/Outbound). This filter can be used in conjunction with all the other existing filters (as shown below).

<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-ae6dbf5c2382d551604c4369df3e138aa491ffd6%2F1ddfbec352d4f80bc393cc86b11010996c5e18ec.png?alt=media" alt="" width="563"></div>
