Roles and Permissions for Access Control
Learn about roles that define a user’s access control permissions in Verkada Command
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 detailed in this article. See Legacy Access Control Roles for more information.
This article describes the set of roles and associated permissions for Verkada Access Control. For more information on roles and permissions for other Verkada product lines, see Roles and Permissions for Command.
Permissions considerations
Subsites inherit permissions from all parent sites, including the ultimate parent.
Users can belong to multiple groups. When roles conflict, the user receives the highest role granted directly or through any group.
Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access.
Permissions for access control are set at both the organizational level and the site level. There are two org-level roles and one site-level role that define a user’s permissions to view and manage access control permissions and devices:
Access control roles are granted to users independently of one another.
Org-level roles
Site-level role
Set permissions
Common access control permission configurations
Scenario
Role Configuration
User needs total control over all access control system settings, devices, and users. For example, a Security Director.
Access System Admin
Access User Admin
User needs to be able to create and edit door schedules or exceptions applied to doors in one or more sites.
For example, a security team member.
Access System Manager
User is responsible for onboarding new users by printing badges and adding them to access groups. For example, an HR staff member.
Access User Manager
User is only responsible for adding credential info and printing badges for new users, such as SCIM-synced users. For example, an HR staff member.
User needs to manage all site-specific access control settings but should not be able to edit user or access group settings (granted by User Management Roles). For example, an office General Manager.
Access Site Admin
User needs to manage which access groups have access to doors for a particular site but should not be able to edit other access control settings for the site. For example, an office facilities staff member.
User only needs to view and unlock certain doors for a particular site. For example, a front desk receptionist.
Revisions
11/14/2024:
Added the new Access System, Access User Management, and Access Site roles.
Removed the legacy Access Control Admin, Access Control Manager, and Access Site Admin roles. See Legacy Access Control Roles for more information.
Need more help? Contact Verkada Support.
Last updated
Was this helpful?




