# Legacy Access Control Roles

{% hint style="success" %}
As of November 14, 2024, access control permissions have changed. Users with legacy access control roles will maintain their permissions until they are updated to the current roles. Users added or modified after this date will be granted the new access control permissions. [See Roles and Permissions for Access Control](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) for more information.
{% endhint %}

There are two sets of legacy roles that define a user’s permissions to view and manage access control within Command:

* **Access role (legacy)**. This role is set at the org level, either Access Manager or Access Admin.
* **Access Site Admin (legacy)**. This role is set at the site level for each site. For a user to be an Access Site Admin of any site, their access control role must be set to either Access Manager or Access Admin.

{% hint style="warning" %}
If a user has a legacy access control role, they need to [migrate to the current roles](#h_f4e9888012) before any changes to their access control permissions can be made.
{% endhint %}

***

## Permissions comparison

Below are diagrams comparing the permissions of the legacy access control roles (shown in blue) to the [current access control roles](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) (shown in white).

### Org-Level Access System Permissions

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-08d817a83c1adc725b6b4abe4afad743dd0c3cdc%2F5b5eca8528a1efd01808c8c42a36d43dc89bf987.png?alt=media)

### Org-Level Access User Management Permissions

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-76859f034296ee1a683e0cb63835c2f5cfecb430%2F7c657c3167d6cc60fa8557920d4ac76e7a849ed0.png?alt=media)

### Site-Level Access Control Permissions

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-489f4d7e511b1006632cdc89e6867327b9a94ef8%2F3c3ed94d5b6b643bd1e1264161e0aafc11d1b658.png?alt=media)

***

### Detailed Legacy Role Descriptions

<details>

<summary>Access Manager</summary>

A user with their org-level access control role set to Access Manager can:

* Do everything an [Access Member](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) can do.
* Unlock the doors they have been given access to.
* View, add, suspend, and edit access users, including updating user information (not synced via SCIM), granting and suspending access, and adding and deleting credentials.
* View, edit, and delete access groups (not synced via SCIM).
* View, edit, and delete buildings.
* View, edit, delete, and add floors within buildings.
* If you are an Org Admin, view the descriptions of and delete saved event reports created by other users.

For the sites that an Access Manager is an Access Site Admin of, they can:

* View and unlock doors.
* Change the schedule for a door to a door schedule that has already been created.
* To a door, add a door schedule exception that has already been created.
* View live and historical access events. Run, save, export, and distribute reports of these events. Add and edit alerts based on access events.

</details>

<details>

<summary>Access Admin</summary>

A user with their org-level access control role set to Access Admin can:

* Everything an Access Manager can do.
* View, add, edit, and delete access groups (not synced via SCIM).
* View, add, delete, and edit door schedules, door schedule exceptions, and access schedule exceptions.
* Update the [Access role](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) of other users.
* For any sites that the user has visibility into, update the [Access Site Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) role of other users.
* Configure org-wide access settings, such as Bluetooth unlock.

For the sites that an Access Admin is an Access Site Admin of, they can:

* Perform everything an Access Manager can do.
* Add, edit, and delete doors, AUX inputs/outputs, lockdowns, and access controllers.
* Add, edit, and delete access levels and access schedule exceptions.
* Manage site-level access settings, such as Bluetooth unlock and scheduled firmware updates.

</details>

### Access Site Admin

When a user is an Access Site Admin of a given site, their permissions for that site depend on whether their org-level access control role is as an Access Manager or Access Admin. The following table outlines which permissions are granted when a user is made an Access Site Admin of a given **Site X**:

|                                                                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                          |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Access Manager**                                                                                                                                                                                                                                                                                                                                                 | **Access** **Admin**                                                                                                                                                                                                                                                                                                     |
| <p>View live door events for doors in Site X</p><p>View reports for doors in Site X</p><p>View door event history</p><p>View user event history for doors in Site X</p><p>Change the schedule for a door in Site X to another schedule that already exists</p><p>Override the schedule for a door in Site X</p><p>Unlock a door in Site X from Verkada Command</p> | <p>Does everything an Access Manager can, in addition to:</p><p>Change the Access Role of other users</p><p>Add/remove Access Site Admins for Site X</p><p>Add/remove access control devices in Site X</p><p>Add/configure/remove doors and AUX devices in Site X</p><p>Add/configure/remove access levels in Site X</p> |

{% hint style="danger" %}
Access Admins who are not also Org Admins cannot grant themselves Access Site Admin permissions.
{% endhint %}

***

## Migrate legacy access control roles

{% hint style="danger" %}
You must be an Org Admin or **both** an [Access System Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) **and** [Access User Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) to migrate a user with legacy access control roles to the current access control roles.
{% endhint %}

{% stepper %}
{% step %}

#### In Verkada Command, go to **All Products** > **Admin** .

{% endstep %}

{% step %}

#### Under **Org Settings**, select **Users**.

{% endstep %}

{% step %}

#### Select the user with a legacy access control role.

{% endstep %}

{% step %}

#### On the left side panel, next to **Access Control Roles**, click **Update Roles**.

{% endstep %}

{% step %}

#### Click **Assign New Roles**.

a. Select the Access System, Access User Management, and Access Site roles that you want the user to have.\
b. Click **Finish and Apply Roles**.
{% endstep %}
{% endstepper %}

After migrating the new access control roles, all of the user’s legacy access control roles will be removed. Going forward only the current access control roles can be granted to this user.

***

### FAQ

<details>

<summary>What if a user with legacy access control roles is added to a Command group that grants them current access control roles?</summary>

If a user with legacy access control roles is added to a [Command group](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/users-and-permissions/manage-command-groups) that has current access control roles, then the user will receive all permissions granted to them by the combination of their legacy and current access control roles.

While this state is supported, it’s recommended to migrate a user’s legacy access roles to the current access control roles before assigning permissions through a Command group. This helps streamline tracking of the user’s current access permissions.

</details>

{% hint style="success" %}
**Need more help?** Contact [Verkada Support](https://www.verkada.com/contact/).
{% endhint %}
