> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/configuration/configure-the-ax11-io-controller.md).

# Configure the AX11 IO Controller

Learn how to setup and configure the Verkada AX11 IO Controller

You can use Verkada’s [AX11 IO Controller](https://docs.verkada.com/docs/io-controller-ax11-datasheet.pdf) to integrate multiple, additional third-party sensors, switches, and peripherals, which can then be managed through [Verkada Command](/command/getting-started/get-started-with-verkada-command.md) in our intuitive centralized web-based interface.

With 16 inputs and 16 outputs, the AX11 IO controller is designed to add flexibility to existing access control systems. You have more options available to remotely lock or unlock doors, monitor entryways, and secure critical assets. Moreover, events generated by the AX11 can be cross-referenced with [security camera](https://www.verkada.com/surveillance/) footage and ingested by our [alarms and professional monitoring](https://www.verkada.com/alarms/) offering to make any Verkada deployment even more integrated and scalable.

{% hint style="info" %}
Follow the steps in this [guide](https://docs.verkada.com/docs/access-control-ax11-installation-guide.pdf) for the hardware installation steps.
{% endhint %}

***

## Add the AX11 IO controller to Command

{% stepper %}
{% step %}
[**Add the device**](/command/organization-settings/add-a-device-to-your-command-organization.md) **to Command.**
{% endstep %}

{% step %}
**In Command, go to All Products > Devices.**
{% endstep %}

{% step %}
**Select your AX11 device and click Set Up to configure.**
{% endstep %}

{% step %}
**Click Apply.**
{% endstep %}

{% step %}
**From the AX11’s device page, click Add and select the input type:**

a. [Door Monitor](#h_43907903c1)\
b. [Elevators](#h_c958fd5297)\
c. [AUX Input](#h_18ec5b58ba)\
d. [AUX Output](#h_d95c642bb3)
{% endstep %}
{% endstepper %}

***

## Configure your input type

### Door monitor

{% stepper %}
{% step %}
**Under Settings:**

a. Enter a unique name.\
b. Select the desired port for this input.\
c. Click **Next**.
{% endstep %}

{% step %}
**(Optional) Toggle on Notify if the door is held open to receive notifications door held open (DHO) notifications on this port.**
{% endstep %}

{% step %}
**(Optional) Toggle on Event Bridge to have this input state mirrored on the same numbered output port.**
{% endstep %}

{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}

### Elevator

{% stepper %}
{% step %}
**On Name, enter a unique name and click Next.**
{% endstep %}

{% step %}
**On Building/Floor, select the building where the elevator is located.**
{% endstep %}

{% step %}
**On Hardware:**

a. Configure the number of readers and which output each floor is connected to.\
b. (Optional) Configure a nearby camera, if needed.
{% endstep %}

{% step %}
**On Settings, configure the desired unlock time and if** [**Verkada Pass**](/access-control/users-and-credentials/verkada-pass-app.md) **remote unlock or** [**Bluetooth unlock**](/access-control/configuration/bluetooth-unlock.md) **is desired.**
{% endstep %}

{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}

### AUX input

{% stepper %}
{% step %}
**Under Settings:**

a. Enter a unique name.\
b. Select the desired name, port, and connection type.\
c. Click **Next**.
{% endstep %}

{% step %}
**(Optional) On Hardware, configure the location and a nearby camera, if needed.**
{% endstep %}

{% step %}
**Under Settings, select the desired Input Type.**

* **Door Unlock** can have a wired input trigger multiple doors to unlock.
* **Lockdown Trigger** can trigger a [lockdown scenario](/access-control/emergency-response/emergency-lockdown.md) for an access site.\
  ​\
  ​**Required.** You must have a lockdown scenario preconfigured before you can use the Lockdown Trigger input type.\
  ​
* **AUX monitors** allows you to log events when the input signal is high. For the AUX monitor input type, toggle on the desired settings.\
  ​\
  ​**Note**: You can go back and add a camera to this input to gain more context on this triggered event. If you already left this setup window, you can add the camera on the input’s **Settings** page.
  {% endstep %}

{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}

### AUX output

Follow the instructions described in [Configure an AUX Output on an Access Controller.](/access-control/configuration/configure-the-ax11-io-controller/configure-an-aux-output-on-an-access-controller.md)

***

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/access-control/configuration/configure-the-ax11-io-controller.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.