Ctrlk
Quick LinksLog InContact Support
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Keycode Management

Learn about keycode management in Verkada Alarms

This article is a guide for New Alarms. Refer to this article if you have classic Alarms. See New Alarms vs Classic Alarms if you are unsure which version of Alarms you have.

With keycode management, each user has one keycode associated with their Command profile. Users can use their keycode at any alarm site where they have arm/disarm access. This provides three key benefits:

  • One keycode across sites: Users can use the same keycode at every alarm site where they have arm/disarm access. You do not need to configure a separate keycode for each site.

  • Manage access through users and groups: Grant arm/disarm access directly to a Command user or group. Access can apply to specific partitions, an entire site, or multiple sites.

  • Clear visibility with the Alarm User role: The Alarm User role makes it easy to see who has arm/disarm access to each site or partition.

Permissions

Org Admins and Site Admins automatically inherit Alarm User (Site) role permissions:

  • Org Admins can arm/disarm all partitions across all sites in the organization via Command and keypad.

  • Site Admins can arm/disarm all partitions site-wide via Command and keypad, but only for the sites where they are a Site Admin.

This does not apply to temporary Organization Admins or Site Admins.

Migrate to unified keycode management

Select the Migrate to a new keycode experience banner in Command to review your organization’s migration status. If you take no action, Verkada will automatically migrate your organization after November 9, 2026.

Before your organization can migrate to unified keycode management, Command checks for previous keycode conflicts:

No conflicts found

Your organization can migrate immediately. Select Migrate to start using unified keycode management.

Conflicts found

Command displays the conflicts that must be resolved. Only Org Admins can download the conflict report and resolve these conflicts. If you take no action, Verkada will force-migrate your organization on December 7, 2026.

There are three types of conflicts:

All conflicts must be resolved before your organization can migrate.

  1. The same user has different keycodes at different sites

    Choose one keycode for the user and update their keycode at each alarm site so it is the same across all sites.

  2. Two or more users have the same keycode

    Assign each user a unique keycode so that no two users share the same keycode.

  3. A user’s keycode matches a general keycode

    Update either the user’s keycode or the general keycode at the affected site so they no longer match.

Contact Verkada Support if you need help resolving conflicts.

Grant Alarm User role permissions

There are three ways to give a user arm/disarm access to a site. See Roles and permissions for more information.

Granting a user the Alarm User role does not automatically generate a keycode for that user. You must generate their keycode separately under the Keycode tab.

1

In Verkada Command, go to All Products > New Alarms.

2

Select your alarm site.

3

In the left navigation, select Keycodes.

4

At the top right, click Add.

  1. Search for and select a user, then click Add.

  2. Once the user is added, select whether to grant site-wide permissions or permissions only to a subset of partitions.

  3. Select Save.

1

In Verkada Command, go to All Products > Admin.

2

Select Users & Permissions > Users.

3

Select a user to grant permissions.

4

Click Manage to the right of Site Roles.

  1. Select Alarm.

  2. Select the Alarm User (Site) role for site-wide access or the Alarm User (Partitions) role for access to specific partitions within the site.

  3. Click Save.

1

In Verkada Command, go to All Products > Admin.

2

Select Users & Permissions > Groups.

3

Select a Command group that has Alarm User role permissions granted. If you need to grant the group permissions:

  1. At the top, click Roles.

  2. Click Manage to the right of Site Roles.

    1. Select Alarm.

    2. Select the Alarm User (Site) role for site-wide access or the Alarm User (Partitions) role for access to specific partitions within the site.

    3. Click Save.

4

At the top, click Members > Add Member.

  1. Search for and select a user.

  2. Click Done.

A group’s access can apply to:

  • An entire site.

  • One or more partitions within a site.

  • Multiple sites through an organization-based group.

  • By default, the user receives the Alarm User (Site) role and can arm and disarm all partitions.

  • To limit access to specific partitions, click Site-Wide in the Partitions column. Clear All partitions, then select the partitions the user should be able to arm and disarm. The role automatically changes to Alarm User (Partition).

  • A site-wide role allows the user to arm and disarm through both Command and keypads. A partition-scoped role allows the user to arm and disarm only via keypads and does not provide Command access.

Manage keycodes

1

In Verkada Command, go to All Products > New Alarms.

2

Select your alarm site.

3

In the left navigation, select Keycodes.

4

Select the user > Keycodes.

5

To the right of a user's keycode, select Regenerate to generate a random keycode, or select Edit to enter your own keycode.

1

In Verkada Command, go to All Products > New Alarms.

2

Select your alarm site.

3

In the left navigation, select Keycodes.

4

Select the user > Keycodes.

5

To the right of a user's keycode, click Delete.

This removes the Alarm User role for the user on that site.

General and duress keycodes

General keycodes and duress keycodes remain site-scoped. Add and manage both from the General Credentials and Duress Keycode tabs on the alarm site's Keycodes page.

See Configure New Alarm Site Settings for more information.

Last updated

Was this helpful?