Roles and Permissions for New Alarms

Learn about the roles and user permissions granted for Verkada Alarms

This article describes the set of roles and associated permissions for Verkada Alarms. For more information on roles and permissions for other Verkada product lines, see Roles and Permissions for Command.

  • Site-level roles determine the access a user or group has to devices in the site.

  • 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.


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.


New Alarms roles

Arm / Disarm

Users with this role can arm and disarm the site and resolve alarms through Command (web or mobile). They cannot access the alarm site configuration or other products unless explicitly granted permission.

This role is suited for users such as guards, cleaning staff, or contractors who need basic permissions to arm or disarm the alarm system without broader site or product access.

Unassigned

This is the default role for users without an assigned New Alarms role. Users with this role cannot arm and disarm, access the alarm site configuration, or access other products.


Site-level roles

No Access
  • Cannot view the alarm site.

  • If added as a response contact for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.

Site Viewer
  • Cannot create or edit an alarm site.

  • Cannot arm or disarm alarm sites or resolve an alarm via Command.

  • Can view all alarm activity and event history with historical footage and live streams.

  • If added as a response contact for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.

Site Admin
  • Can create or edit an alarm site.

  • Can create and edit keycodes along with all other alarm configurations.

  • Can arm or disarm alarm sites or resolve an alarm via Command.

  • Can add or remove Verkada devices and wired inputs/outputs on the site.

  • Can view all alarm activity and event history with historical video.

  • If added as a response contact for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.


Set permissions

User
  1. In Verkada Command, go to All Products > Admin .

  2. UnderOrg Settings, select Users.

  3. Select a user.

  4. At the top right, click Manage Roles.

    1. Set the needed permissions.

    2. Click Save.

Groups
  1. In Verkada Command, go to All Products > Admin .

  2. Under Org Settings, select Groups.

  3. Select a group.

  4. At the top, select Site Roles > Manage Roles.

    1. Set the needed permissions.

    2. Click Save.

Sites
  1. In Verkada Command, go to All Products > Admin .

  2. In the left navigation, select Sites.

  3. Select a site to manage and in the right pane, click Manage .

    1. In the top right, click Add to add a new user or group.

    2. Select an existing user or group to edit their permissions.


Common Alarm permission configurations

Scenario

Role Configuration

User requires full administrative control of the alarm site.

​For example, a Security Director, Facilities Manager.

Site Admin

User can view alarm incidents for investigation and arm or disarm the system through Command (web or mobile), but cannot modify the site configuration. ​ ​For example, a SOC team member.

Site Viewer + Arm/Disarm

User can only arm and disarm the site through Command (web or mobile) and has no access to the alarm site or other products within it.

For example, a guard, janitor, or contractor.

No access + Arm/Disarm

Last updated

Was this helpful?