This article describes the set of roles and associated permissions for Verkada Command. It also explains how to customize roles and permissions.
Permissions are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites/subsites.
User permissions specify what tasks users can perform and what features users can access in Command.
Site-level permissions define what access a particular user or group has to the cameras within the site. Site-level permissions are configured using roles.
Organization permissions pertain to user management (the ability to access an organization, invite users to an organization.
Note: Because organization, access control, and site permissions serve different purposes, they are separate. However, users need to have permissions set for these levels to have full use of Command.
Permission levels
Permissions are set at the following levels:
Level | Permissions |
Organization | All users added to the organization have the ability to log in to the Command organization. Only those users designated as an Organization Admin (Org Admin) can invite/delete other users, create sites, and modify all permissions. |
Site | Site-level permissions define what access a particular user or group has to the cameras within the site. Site-level permissions are configured using roles (see below). |
Subsite | Subsite permissions are no different from site-level permissions. The only difference is that subsites inherit the permissions of the subsites and parent sites above them. |
Roles | There are 4 levels of access that a user or group can have to a site or subsite:
|
Permissions considerations
Sites and subsites do not inherit permissions from the organization (being an Org Admin does not automatically make you a Site Admin).
Subsites inherit permissions from all subsites (and the ultimate parent site) above them.
A user can be assigned to multiple groups. If permissions conflict, the user is always granted the highest role granted to them directly, or to one of the groups to which they belong. For example, if a user is assigned to a group which assigns the role Site Viewer for a particular site, but is also assigned to a group which assigns the role Site Admin for that same site, the user will be granted Site Admin permissions for that site.
Permissions can always be upgraded, but never downgraded. For example, if a user is assigned to a group that assigns the role Site Viewer for a particular site, that user may be manually upgraded to Site Admin for that site. However, this user cannot be downgraded to a Live-Only Viewer (or any role below Site Viewer). A user's role can only be downgraded if they are removed from the group which assigns the highest level of access.
Common user permission configurations
Scenario | Configuration Requirement |
View, archive, and take snapshots of footage. |
|
View, archive, share, and take snapshots of footage and modify camera settings, and set other users' permissions (globally). |
|
View, archive, share, and take snapshots of footage and modify camera settings, and set other users' permissions on certain cameras. |
|
View only live streams of cameras. |
|
Roles and permissions by Verkada product
Roles and Permissions for Workplace (Guest and Mailroom)
Org-level roles
Org-level roles are configured on a per-user basis. Groups cannot be used to set org-level roles.
Org member
Org member
All users added to an organization are organization members. A user added to the organization who has not been made an Org Admin has the minimum level of access needed to sign in to the organization.
Access allows you to:
View the organization when logged in.
Configure personal notifications (which alerts the user wants to receive).
Set personal 2-Factor Authentication (2FA) settings.
Org Admin
Org Admin
Any org member can be upgraded to an Org Admin.
Access allows you to:
View the organization when logged in.
Configure personal notifications (which alerts the user wants to receive).
Set personal and org-wide 2FA settings.
Create floor plans.
Add, delete, and modify access users.
Set user and group permissions for the org and all sites/subsites.
Configure org-wide settings, including maximum archive duration, enable/disable cloud backup globally, and default camera playback quality.
Rename or delete the org.
Create new sites and subsites.
Add and remove cameras to the org.
Adjust camera stream encoding settings.
Access Control Role
Access Control Role
This role is set at the org level and can be set to Access Control Member, Access Control Manager, or Access Control Admin. See permission details in Roles and Permissions for Access Control.
Site-level roles
Site-level roles can be assigned to individual users or to groups and pertain to a specific site or subsite. Subsites inherit the permissions from the subsites and parent sites above them.
No Access
No Access
Users and groups do not have access to the site or subsite's camera live feeds, historical video, or archives.
Site Live-Only Viewer
Site Live-Only Viewer
Permits users to only view live streams (no access to historical video) of the cameras within the site/subsite. Access allows you to:
View individual camera live streams.
Utilize digital zoom.
Create and view grids.
View floor plans.
Site Viewer
Site Viewer
Site viewers can access live and recorded footage for cameras within the site or subsite. Access allows you to:
View live streams.
Utilize digital zoom.
View historical video.
Perform motion searches.
View camera settings.
View camera stats.
Take live feed snapshots.
Archive and download video (non-private archives only).
Site Admin
Site Admin
Site Admins can access live and recorded footage for cameras within the sites/subsites they have permissions for and can also configure site/subsite permissions and camera settings. Access allows you to:
Add, delete, and set user permissions on a site (user must be added to org first).
Add cameras to the organization and to sites for which the user is Site Admin.
Remove cameras from the organization only from sites for which the user is Site Admin.
Create, rename, and delete sites and subsites.
View live streams.
Share live links (SMS and link).
View historical video.
Perform motion searches.
Take live feed snapshots.
Archive video and download as mp4.
Note: Site Admins can only view non-private archives. Organization Admin permissions are also needed to view private archives.
Configure camera settings including name, orientation, and location.
Utilize auto and manual focus.
Utilize optical and digital zoom.
Access and configure additional settings including custom focal point, cloud backup, motion events, and audio.
Create camera embeds.
View camera stats.
Note: Site Admins cannot edit sites or subsites they have not been granted permissions for.
Access Site Admin
Access Site Admin
This role is set at the site level and can be turned on or off for each site. In order for a user to be an Access Site Admin of any site, their Access Control Role must be set to either Access Control Manager or Access Control Admin. See permission details in Roles and Permissions for Access Control.
Customize Roles and Permissions
Verkada's Roles & Permissions Customization feature enables Org Admins the ability to add or remove certain permissions from Site Admins and Site Viewers more granularly. Some organizations may want to limit or extend the permissions of the members of their organization based on their needs. Currently, we allow customization of permissions related to archives, link sharing, and user management.
In Verkada Command, go to All Products > Admin.
At the top, select Org Settings > Roles & Permissions Customization.
Manage your roles and permissions:
For Camera Roles, click Edit to configure the camera permissions that you want to grant to different roles.
For Admin Roles, click Edit to configure the admin permissions that you want to grant to different roles.
Click Save when you've completed your settings.
You should see the current permissions that Site Viewers and Site Admins have, adjust these permissions, or click Restore Default Settings to return to the default if desired. Changes apply to all Site Admins and Site Viewers in the org.
FAQ
Why has my organization disappeared?
Why has my organization disappeared?
A user must be a member at the org level to see the organization in the dropdown when they log in. If a user is a member of an organization, they appear on the user list that Org Admins and Site Admins can access in Command.
If your organization disappeared, it can be due to one of these reasons:
Your user account was removed from the organization.
The organization was deleted.
Troubleshoot
If you are the affected user, contact the Org Admin and request to re-add you to the organization.
If a user has reported this to you, verify they are a member of the organization.
Why are cameras missing from my organization?
Why are cameras missing from my organization?
Sites do not inherit users from the organization or other sites. Users who are members of the organization cannot see cameras unless they have explicitly been granted permissions to the site or sub-site where the cameras reside.
If you are the affected user, contact the Org Admin or Site Admin and request access to the desired sites and subsites.
If a user has reported this to you, grant them access to the desired sites and subsites.
Why can't I access certain features or settings, such as other users?
Why can't I access certain features or settings, such as other users?
If you are unable to access certain features or settings, you don't have sufficient permissions. Only Admins can access all features and settings.
Org Admins are not automatically escalated to Site Admin for any site. This is a separate feature set. Therefore, Org Admins do not inherently have permission to view any one particular site, but they can assign themselves the required roles to see their desired sites.
Troubleshoot tips:
If you are the affected user, contact the Org Admin or Site Admin and request that they elevate your permissions to Org Admin or the desired site or subsite.
If a user has reported this to you, elevate their permissions on the organization or desired site or subsite.
Related resources
Visit the Verkada Training Center for bite-sized video tutorials on how to accomplish role-based tasks in Command
Need more help? Contact Verkada Support