> 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/access-control-subsites.md).

# Access Control Subsites

## Clone access levels and lockdowns

Verkada recognizes the importance of efficient site management. Nested sites (subsites) in Access Control let you apply the same organizational structure across all Verkada product lines, providing a more streamlined and scalable way to manage your Verkada deployment.

How it works

* If a Command user is an Access Site Admin for a site, whether top-level or nested, they automatically become an Access Site Admin for all subsites beneath it. Learn more about Roles and Permissions for Access Control.
* Access control devices are assigned to a specific site, either top-level or nested, and are scoped only to that site.
* All doors connected to an access controller belong to the same site as the controller.

{% hint style="warning" %}
See [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md) for more information.
{% endhint %}

***

## Clone access levels and scenarios

To enhance ease of configuration, access levels and emergency scenarios can be cloned. This allows existing access levels and emergency scenarios to be duplicated and placed in other sites, including subsites.

During the cloning process, the following aspects are cloned:

* Access level and scenario configuration
* Access level and scenario settings, rules, and parameters

{% hint style="warning" %}
Doors controlled by an access level or locked/unlocked by an emergency scenario are not cloned. This ensures that the proper door associations are maintained and avoids any unintended consequences during the cloning process.
{% endhint %}

***

## Migration considerations

If you have previously adopted a flat site structure (before subsites), you may want to transition to the new nested site structure.

{% hint style="danger" %}

* When moving an ACU from one site to another, all doors on the ACU lose their access-level associations.
* Doors are removed from any scenarios in the original site.
  {% endhint %}

***

## Troubleshooting tips

* Access levels should be copied over immediately after all door controllers so that doors can be added. This reduces the downtime for these doors and gives immediate access to the correct set of users.
* Clone scenarios into all sites where doors are expected to lock down. See [Emergency Scenarios](/access-control/integrations-and-alerts/configure-access-control-event-alerts/emergency-lockdown.md) for more information.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.verkada.com/access-control/configuration/access-control-subsites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.