> 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/move-access-controllers-to-other-sites.md).

# Move Access Controllers to Other Sites

Learn how to move an access controller from one access site to another

Access sites group access controllers and doors for easier management and monitoring. Each access controller must belong to a site or subsite. Controllers are linked to their doors, so moving a controller also moves all of its configured doors.

{% hint style="danger" %}
You must be an [Access Site Admin](/access-control/getting-started/roles-and-permissions-for-access-control.md) for both the current site and the destination site to change an access controller’s site.
{% endhint %}

***

## Configuration

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

{% step %}
**At the top, search for "device type": "Access Controller" to see a list of all your access controllers.**
{% endstep %}

{% step %}
**Select the controller you want to move, then on the right click** <i class="fa-right">:right:</i>.
{% endstep %}

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

1. Next to **Sites**, select the name of the current site.
2. On **Change** **Site**, select the site you want to move the controller to and click **Save**.
3. On **Move Access Controller**, select whether to keep the current access levels, alerts, and lockdowns or remove them from the controller and click **Confirm**.
   {% endstep %}
   {% endstepper %}


---

# 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/move-access-controllers-to-other-sites.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.