> 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-a-door-in-command/add-a-door-to-an-access-controller.md).

# Add a Door to an Access Controller

Adding a door to your Verkada access control system

A door consists of all the configurations and components connected to an access controller on a particular cassette.

{% hint style="danger" %}
You must be an Access Site Admin to add a door. Learn more about [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md).
{% endhint %}

{% stepper %}
{% step %}
**On the AC41, there are four cassettes, labeled 1 to 4, that correlate to each door.**

<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-562f1a2d411a71cc30f1ce3d7674af30c8c94356%2Fe260d76eae5f313fddef92200af204ce75a9224d.png?alt=media" alt="" width="516"></div>
{% endstep %}

{% step %}
**Configure a door: Find the number of the door wired to the associated cassette.**
{% endstep %}

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

{% step %}
**Find the Verkada Access Controller you want to add doors to.**
{% endstep %}

{% step %}
**At the right, select the access controller.**
{% endstep %}

{% step %}
**At the top right, click Add.**
{% endstep %}

{% step %}
**From the setup list, click Door.**
{% endstep %}

{% step %}
**Follow the configuration steps to add a name and the components that are installed.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Only check the **REX** (Request to Exit) or **DPI** (Door Position Indicator) box if they are installed and you want the REX sensor/button to unlock the door (this is typically the case with magnetic locks).
{% endhint %}

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=reGRRopgx7Q).
{% 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-a-door-in-command/add-a-door-to-an-access-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.