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

# Add an Access Controller

Learn how to add an access controller to your Command account

### Before you begin

Verkada access controllers connect to your building's existing door hardware and readers to manage access. Once connected, you can use Verkada Command to manage doors, users, and schedules from any device. 

Integrations with Active Directory platforms automatically configure, onboard, and offboard employees. Verkada Command also pairs access control with cameras to deliver real-time video analytics, helping you monitor entry points and respond quickly to important events.

***

## Claim your access controller

{% hint style="danger" %}
You need Org Admin permissions to add an access controller to Command.
{% endhint %}

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

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

{% step %}
**Enter the serial numbers or order numbers of the devices.**
{% endstep %}

{% step %}
**Click Add (X) Device(s). The newly added devices will display on Devices > My Unassigned Devices.**

Once you’ve claimed your Verkada access controller, the **Access** portion of Command will appear, allowing you to manage doors and access controllers.
{% endstep %}
{% endstepper %}

***

## Set up an access controller

You need to assign a device to a site and complete the setup to move it from the **Unassigned Devices** list. Devices can be set up individually or in bulk.

{% stepper %}
{% step %}
**In Verkada Command, select All Products > Devices.**
{% endstep %}

{% step %}
**Under All Unassigned Devices:**

1. Select the device(s) you want to set up.
2. Click **Set Up**.

{% hint style="danger" %}
You can only set up one product type at a time. If devices from multiple product lines are selected, you will not see the **Set Up** option.
{% endhint %}
{% endstep %}

{% step %}
**Under General:**

1. Enter a unique name.
2. Select a **Device Mode.**
3. Select a timezone.
   {% endstep %}

{% step %}
**Under Location:**

1. Select a site.
2. Select a building and floor.
   {% endstep %}

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

* Click **View Device** to set up entities:
  * [Door](/access-control/configuration/configure-a-door-in-command/add-a-door-to-an-access-controller.md)
  * [In/Out Door](/access-control/installation/wire-a-door-to-a-verkada-access-controller/set-up-an-inout-door-with-two-readers.md)
  * [Aux Input](/access-control/emergency-response/emergency-lockdown.md)
  * [Aux Output](/access-control/configuration/configure-the-ax11-io-controller/configure-an-aux-output-on-an-access-controller.md)
* Click **Done** to return to the Devices page.
  {% endstep %}
  {% endstepper %}

***

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