> 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/decommission-an-access-controller.md).

# Decommission an Access Controller

Learn how to factory reset an access controller

To decommission or reset your access controller to factory settings, you first need to remove it from Command. This also deletes all user-related data from the controller and allows it to be transferred to a new organization.

{% hint style="danger" %}
To decommission or reset your access controller to factory settings, you must be an Org Admin, an Access System Admin, or an Access Site Admin for the controller's site. Learn more about the [Roles and Permissions for Command](/command/users-and-permissions/roles-and-permissions-for-command.md) and specifically for [Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md).
{% endhint %}

***

## Process

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

{% step %}
**From the device list, select the controller you want to decommission.**
{% endstep %}

{% step %}
**On the right, click the device.**
{% endstep %}

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

1. At the bottom left, click **Decommission.**
2. When prompted, enter the generated verification code to complete the request.
3. Click **Confirm**.

{% hint style="danger" %}
Decommissioning also removes associated doors. This cannot be undone.
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Wait 5 minutes before adding the controller to another organization.
{% 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/decommission-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.