> 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/installation/access-control-deployment-best-practices/mount-an-ac12.md).

# Mount an AC12

Learn how to configure a PoE passthrough on the AC12 one-door controller

The [Verkada access controller](https://docs.verkada.com/docs/access-control-datasheet.pdf) physically connects to door components to manage access. Access controllers work with your building’s existing door hardware and readers.

## Before you begin

### Verify the contents of your box

* AC12 access controller
* AC12 top hat cover
* mount plate
* T10 security Torx screwdriver
* 2 grommets
* Grommet punch
* 4 drywall screws
* 4 drywall anchors
* 4 M4x18mm machine screws
* 4 8–32¾" machine screws

### Verify the tools you need

* A working internet connection
* A smartphone or laptop
* A #2 Phillips head and power drill
* A level

## Mount the AC12

Decide how you want to mount the Verkada [AC12](https://docs.verkada.com/docs/access-control-ac12-quick-start-guide.pdf) one-door controller. You can mount it flush to the wall with the included bracket or using any sized junction box.

{% hint style="info" %}
We recommend to use the Verkada Square Junction Box (ACC-MNT-11) for the best aesthetic look.
{% endhint %}

{% stepper %}
{% step %}
**Choose how you want to mount the AC12. There are 2 ways:**

* **Option 1**: Mount to the junction box where all wires to come from the center hole.

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2FmOOCFxGkSMl8PSFlb116%2FScreenshot%202026-01-15%20at%202.45.19%E2%80%AFPM.png?alt=media&amp;token=96d8849f-95e7-4aeb-8c01-fe8f5040b60d" alt=""><figcaption></figcaption></figure></div>

* **Option 2**: Mount directly to the wall where all wires come from the closest outer edges.

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2F39tMUPe5ik1Jm7N5nqJg%2FScreenshot%202026-01-15%20at%202.45.48%E2%80%AFPM.png?alt=media&amp;token=0030f927-7d2b-4298-a42c-ae9731bf398f" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Ensure that the hinges are lined up tightly with the mount plate and slide downward into place.**

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2FElHU8JZCVUDzs7YVRTzS%2FScreenshot%202026-01-15%20at%202.45.59%E2%80%AFPM.png?alt=media&amp;token=54a51d7a-e12a-4eec-a810-c06ecb19273e" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Remove the AC12 Top Hat and mount. You’ll need to loosen the 2 blue security screws. These are held in place by springs and don’t need to be completely removed.**

<div align="left" data-with-frame="true"><figure><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2FLYQuveDkznQ3JBlXgxi0%2FScreenshot%202026-01-15%20at%202.46.05%E2%80%AFPM.png?alt=media&amp;token=a5d211aa-f4f2-48b8-a629-8058905995ed" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
You must route the wires through the hole of the AC12 before plugging in blocks, or you need to unplug them to fit the top hat back on.
{% 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/installation/access-control-deployment-best-practices/mount-an-ac12.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.
