For the complete documentation index, see llms.txt. This page is also available as Markdown.

Access Control Subsites

Learn how to manage your 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.


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


Migration considerations

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


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 for more information.

Last updated

Was this helpful?