| Role | Scope | Key User Management Permissions |
|---|---|---|
| Org Admin | Organization-wide | Create and delete Directories. Manage all users and Command groups, including deactivating users, deleting users, and permanently removing users. |
| Command User Admin | Organization-wide | Create and edit users and Command groups across Global and all Directories. Deactivate users, delete users, and remove users from Directories. Cannot permanently remove users. |
| Command User Viewer | Organization-wide | View users and groups. |
| Access User Admin | Organization-wide | Create, edit, and delete users and Command groups in Global and across all Directories. |
| Access User Manager | Organization-wide | Edit users and access group memberships in Global and across all Directories. |
| Access Credential Manager | Organization-wide | Edit and delete user credentials (cards, PINs, mobile unlocks) in Global and across all Directories. |
| Command User Admin | Directory | Create and edit users and Command groups within the Directory. Remove users from the Directory (users revert to Global) or deactivate users. Cannot delete or permanently remove users. |
| Command User Viewer* | Directory | View users and groups within the relevant Directory. |
| Access User Admin | Directory | Create and edit users and access groups within the Directory. Remove users from the Directory (users revert to Global). Cannot de-activate, delete or permanently remove users. |
| Access User Manager | Directory | Create users and credentials. Manage group membership within the Directory. |
| Access Credential Manager | Directory | Create and edit user credentials within the Directory. |
Organization Admin
Any organization member can be upgraded to an Organization 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 organization 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 devices. * Adjust camera stream encoding settings. {% hint style="warning" %} If the [Global Site Admin](/command/users-and-permissions/roles-and-permissions-for-command/customize-roles-and-permissions) policy is enabled, all Org Admins will automatically be granted Site Admin access to all sites. {% endhint %}Organization member
All users added to an organization are organization members. A user added to the organization who does not have admin permissions 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.Command User Admin
{% hint style="warning" %} Command User Admins cannot modify the Organization Admin role. They can assign or remove Command User Admins but cannot elevate or lower Organization Admin permissions. {% endhint %} Any organization member can be upgraded to a Command User Admin. Command User Admin allows you to: * Add and remove users, designate their roles, and assign them to groups. * Add and remove groups and assign users to groups. * Add and remove contacts for individuals outside of your organization. * Create and assign alerts to groups and users in the organization. * Manage and restrict access to Shared Links for users in the organization. * Enable Support Access.Command User Viewer
Command User Viewer allows you to: * View users, their roles, and their groups. * View groups, their roles, and their users.Site Admin
**Cameras** Site Admins can access live and recorded footage for cameras within the sites for which they have permissions. They can also configure site permissions and camera settings. Site Admins can: * Add, remove, and manage user permissions on a site for existing users * Add cameras to the organization and to any site where they are a Site Admin * Delete cameras from the organization only from sites where they are a Site Admin * Create, rename, and delete sites and subsites * View live streams * Share live links (SMS and link) * View historical video * Archive video and download as an MP4 * View non-private archives. {% hint style="danger" %} You need Org Admin permissions to view private archives. {% endhint %} * Perform motion searches * Take live feed snapshots * Configure camera settings * Utilize auto and manual focus * Utilize optical and digital zoom * Create camera embeds * View camera stats * Has full access to controls and features, including Sentry Mode for PTZ cameras **Alarms** * 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 **Air Quality Sensors** * Add or remove sensors, move them between sites you administer, and reboot hardware * Turn triggers on or off, edit trigger settings and sensitivity, receive offline alerts for sensors on accessible sites, and link a context camera (requires Site Admin permissions for the camera's site) * Download sensor readings as a CSV and, for supported SV25 units with the feature enabled, use live and recorded audio * Pair dashboards with displays, share or delete dashboards, create tiles using sensor readings and time ranges, and remove tiles as needed * View sensor readings across accessible sites, filter and sort readings by type and time range, and switch between sites **Gateway** * Open gateway details, run a speed test, and see connected devices * Review power history, activity logs, and data graphs * Set up alerts * Claim, set up, manage, identify, reboot, and delete devices on the site * Manage data licenses * Open the gateway home page * Run packet capture, power cycle ports, and switch a gateway to WAN mode * Claim connected devices, change network settings, and toggle smart data usage **Intercom** * Receive calls with video * See 24/7 live intercom video, even if not on an active call * View historical video and events * Unlock the door both during and outside of a call * Unlock the door 24/7 * Talk down to the intercom * Change Receivers and device settingsSite Viewer
**Cameras** A Site Viewer can access live and recorded footage for cameras in the site. Site Viewers can: * 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) * For PTZ cameras, a Site Viewer has full access to controls but limited access to features and settings * Can view existing settings * Cannot enable, disable, or edit Sentry Mode settings **Alarms** * 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 **Air Quality Sensors** * View the sensors in the site * View analytics values for the sensors in the site * Toggle between different durations (live, today, this week, etc.) * View dashboards **Gateway** * Open gateway details, run a speed test, and see connected devices * Review power history, activity logs, and data graphs * Set up alerts **Intercom** * Receive calls with video * See 24/7 live intercom video, even if not on an active call * View historical video and eventsLive-Only Viewer
**Cameras** Live-Only Viewers can **only** view live streams (no access to historical video) of the cameras in the site. Live-Only Viewers can: * View individual camera live streams * Utilize digital zoom * Create and view grids * View floor plans * Has no access to controls or Sentry Mode for PTZ cameras **Alarms** * 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 **Intercom** * Receive calls with video * See 24/7 live intercom video, even if not on an active callUsers
#### Grant permissions 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 Organization Roles, User Management Roles, Site Roles, or Custom Roles. 1. For site roles, select the relevant type (product-specific role or custom role). 2. Select the role to grant to the user. 3. Click **Save**. #### Revoke permissions 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Users.** 3. Select a user to revoke permissions. 4. Click **Manage** to the right of Organization Roles, User Management Roles, Site Roles, or Custom Roles. 1. For site roles, select the relevant product. 2. De-select the role to remove from the user. 3. Click **Save**.Groups
#### **Granting permissions** 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Groups.** 3. Select a Command group to grant permissions. 4. At the top, click **Roles.** 5. Click **Manage** to the right of Organization Roles, User Management Roles, Site Roles, or Custom Roles. 1. For site roles, select the relevant product. 2. Select the role to grant to the group. 3. Click **Save**. #### **Revoking permissions** 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Groups.** 3. Select a Command group to revoke permissions. 4. At the top, click **Roles.** 5. Click **Manage** to the right of Organization Roles, User Management Roles, Site Roles, or Custom Roles. 1. For site roles, select the relevant type (product-specific role or custom role). 2. De-select the role to remove from the group. 3. Click **Save**.Why has my organization disappeared?
A user must be a member at the organization 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 Organization 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 Organization 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?
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 Organization 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?
If you are unable to access certain features or settings, you don’t have sufficient permissions. Only Admins can access all features and settings. Organization Admins are not automatically escalated to Site Admin for any site. This is a separate feature set. Therefore, Organization 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 Organization Admin or Site Admin and request that they elevate your permissions to Organization 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.Users
#### Grant permissions 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. From a list of role types, select **Custom.** 2. Click **Save**. #### Revoke permissions 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Users.** 3. Select a user to revoke permissions. 4. Click **Manage** to the right of **Site Roles** 1. From a list of role types, select **Custom.** 2. De-select the role to remove from the user. 3. Click **Save**.Groups
#### **Granting permissions** 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Groups.** 3. Select a Command group to grant permissions. 4. At the top, click **Roles.** 5. Click **Manage** to the right of **Site Roles** 1. From a list of role types, select **Custom.** 2. Click **Save**. #### **Revoking permissions** 1. In Verkada Command, go to **All Products > Admin.** 2. Select **Users & Permissions** > **Groups.** 3. Select a Command group to revoke permissions. 4. At the top, click **Roles.** 5. Click **Manage** to the right of **Site Roles** 1. From a list of role types, select **Custom.** 2. De-select the role to remove from the group. 3. Click **Save**.Okta
1. Log in to your Okta admin account. 2. On the left, click **Directory > Profile Editor**. 3. Open **Verkada SSO OIDC User**. 4. Select **Add Attribute**: 1. Add the Display name and Variable name (both values are the same) from the org\_secret.txt file. It starts with "vkdae2ee…" 2. Click **Save** 5. Select **Mappings**: 1. Click **Okta User to Verkada SSO OIDC** 2. Copy the encryption key value (the second value in the .txt file, including quotation marks) 3. At the bottom of the Mappings page, paste into the text box for the new variable 4. Click the icon in the middle and select **Apply mapping on user create and update** 5. Click **Save Mappings**, then **Apply updates now** {% hint style="danger" %} Completing the mapping steps correctly is crucial for a seamless ECE camera enrollment process. {% endhint %} {% hint style="info" %} Refer to [Add Custom Profile Attributes](https://support.okta.com/help/s/article/How-To-Add-Custom-Profile-Attributes-As-Claims-In-a-ID-Token-or-userinfo?language=en_US) if you encounter issues. {% endhint %}Microsoft Entra ID (Azure AD)
1. Log in to your Azure portal. 2. Search for and select **App registrations**. 3. Select **Verkada SSO OIDC** (check All applications if not visible). 4. On the left, click **Manage > App roles**: 1. Click **Create app role** 2. Add the **Display Name** and **Description** using the same first value from the `org_secret.txt` file 3. Under **Allowed member types**, select **Users/Groups** 4. **Under Value, enter the encryption key in the format** `first_value:second_value` (without quotes) 5. Click **Apply** 5. On the left, click **Manage > Token Configuration**: 1. Click **Add groups claim** 2. Select **Security groups** as the group type 3. Select **Emit groups as role claims** as the ID 4. Click **Add** 6. On the left, click **Manage > Authentication > Settings**: 1. Under **Implicit grant and hybrid flows**, select both **ID tokens** and **Access tokens** 2. Click **Save** 7. On the left, click **Manage > Manifest**: 1. Verify `idToken.additionalProperties.emit_as_roles` is present 8. Assign users to the new role: 1. Search for and select **Microsoft Entra ID** 2. On the left, click **Manage > Enterprise applications** 3. Click **Verkada SSO OIDC** 4. On the left, click **Manage > Users and groups** 5. Click **Add user/group** 6. Assign users the newly created role 7. Click **Assign**Google Workspace
1. Open your Google Admin console. 2. Navigate to **Directory > Users**. 3. Select **More Options > Manage custom attributes**. 4. Click **Add Custom Attribute** with: 1. Category: **ECEInfo** 2. Custom field: Name: **keys**, Info Type: **Text**, Visibility: **Visible to User and Admin**, No. of Values: **Multi-Value** 3. Click **Add** 5. For each user needing access to your Verkada organization: 1. Go to **Directory > Users** and select a user 2. Expand **User Information > ECEInfo** 3. Click **Edit** 4. Add the display name and encryption key separated by a colon: `What happens if I lose my recovery code?
Your admin can send you a new recovery code from your user account settings.Is my recovery code the same as my invite link?
No. The invite link is used to join the organization. The recovery code is generated after you join and create your password.Can I use my recovery code more than once?
Yes, you can use your recovery code more than once.Create a Verkada Okta app (US regions)
1. **Log in to Okta.** 2. **Go to the Applications page and click Browse App Catalog.**
Configure a new app integration from Okta (EU & AUS regions)
1. **Go to Applications, and select Create App Integration.** 2. **Create a new app integration, select SAML 2.0, and click Next.**
Client ID should be pulled from the Command configuration and replaced in the links inserted in the Okta application.
US region
1. Log in to Okta. 2. On the left navigation panel, click Applications. 3. At the top, click Browse App Catalog.
EU & AUS region
1. Log in to Okta. 2. Go to the Applications page and click Create App Integration.US region
1. Log in to Okta. 2. On the left, click Applications and click the Verkada app. 3. On the left, select the Provisioning tab. 4. Under the Provisioning tab > Integration: 1. Click Configure API Integration. 2. Check the Enable API integration box. 3. In the API Token field, copy and paste your Command-generated API token. 4. Click Save.EU and AUS region
1. Log in to Okta. 2. On the left, click Applications and click the Verkada app. 3. Under the Provisioning tab > Settings: 1. Select To App and click Edit. 2. Check the Enable box for Create Users, Update User Attributes, and Deactivate Users. 3. Click Save. You can add more attributes than shown. See [Add attributes to SCIM-managed users](#add-attributes-to-scim-managed-users).Add attributes to SCIM-managed users (optional)
Verkada and Okta support these attributes: `userName` (default), `givenName` (default), `familyName` (default), `title`, `employeeNumber`, `primaryPhone`, `department`, `organization`. You can also sync a unique identifier to Command by mapping it to the `externalId` field. This enables advanced use cases such as disambiguating users across systems or syncing access credentials to a unique user reference. This value is stored in the database and can be queried via API, but it does not appear in the Command UI. {% hint style="info" %} To provision phone numbers outside the US in Command, include the country code in the user's phone number in the Okta profile. For example: * US: 123-456-7890 → +1 123-456-7890 * UK: 07123 456789 → +44 7123 456789 Using the international format ensures the number is correctly imported into Command. {% endhint %} 1. **Log in to Okta.** 2. **Create the Attribute in the SCIM App Profile.** 1. In Okta, go to **Directory > Profile Editor.** 2. Select your **Verkada SCIM-managed application User.** 3. Click **Add Attribute** and add the attribute details as listed in the [table](#attribute-table) below. 4. Click **Save.**Add access credentials to SCIM-managed users (optional)
1. **Log in to Okta.** 2. **On the left navigation, select Directory > Profile Editor.** 1. Select **User (default)** as the user type. 2. Click **Add Attribute** and add the custom attributes from the [table](#attribute-table) below. 3. **On the left navigation, select Applications and open your Verkada SCIM-managed application.** 4. **On the Provisioning tab, select To App > Go to Profile Editor.** 5. **Click Add Attribute to create the attributes listed above using the exact same Data Type, Display Name, Variable Name, Description, and ENUM values.** 1. Set the **External namespace** value for all attributes to: ``` urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User ``` 2. Set **Attribute type** to **Personal**. 3. Click **Save** to add the attribute. 6. **Click Mappings to map the attributes from the Okta User application to your SCIM application.** 1. Select **Okta User to YourSCIMApp** at the top and map the custom attributes created for the Okta Default User to the ones created on your SCIM application. 2. Click **Save Mappings** and **Apply updates now** to apply the changes.Attribute table
Refer to this list of credentials for the list of [acceptable card formats](/access-control/installation/badge-reader-support/supported-card-formats). Data type for all attributes will be string.| Display Name | Variable Name / External Name | External Namespace | Description | ENUM |
|---|---|---|---|---|
| Card Format | cardFormat | urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User | Card format for access credential | Leave unchecked |
| Card Number | cardNumber | urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User | Card number for access credential | Leave unchecked |
| Card Number Hex | cardNumberHex | urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User | Hexadecimal representation of the card number | Leave unchecked |
| Credential Status | credentialStatus | urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User | Status of the card credential | Checkbox: active → active, deactivated → deactivated, deleted → deleted |
| Facility Code | facilityCode | urn:ietf:params:scim:schemas:extension:verkada:access:2.0:User | Facility code associated with the card | Leave unchecked |
| External ID | externalId | urn:ietf:params:scim:schemas:extension:verkada:core:2.0:User | Customer-defined unique ID, not exposed in UI | Leave unchecked |
| Department ID | costCenter | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User | Identifier used to map user's department in Command | Leave unchecked |
| Title | title | urn:ietf:params:scim:schemas:core:2.0:User | User's title or role | Leave unchecked |
| Employee Number | employeeNumber | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User | Employee ID | Leave unchecked |
| Phone Number | Variable Name: External Name: | urn:ietf:params:scim:schemas:core:2.0:User | Work phone number | Leave unchecked |
| Department | department | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User | User's department | Leave unchecked |
| Organization | organization | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User | Company or organization | Leave unchecked |
Users within Okta
1. Log in to Okta. 2. On the left, click Applications and click the Verkada app. 3. Click the Assignments tab. 4. Click the Assign dropdown and select Assign to People. 5. Click Assign for the people you want to provision to the app. 6. You'll see the information for that user. At the bottom, click Save and Go Back. 7. When you are redirected to the Assign page, click Done.Groups within Okta
1. Log in to Okta. 2. On the left, click Applications and click the Verkada app. 3. Click the Assign dropdown and select Assign to Groups. 4. Click Assign for the groups you want to provision to the app. 5. You'll see the information for that group. At the bottom, click Save and Go Back. 6. When you are redirected to the Assign page, click Done. 7. At the top, select the Push Groups tab. 8. Click the Push Groups dropdown to find groups (by name or by rule).
https://www.googleapis.com/auth/admin.directory.user.readonly,
https://www.googleapis.com/auth/admin.directory.group.readonly,
https://www.googleapis.com/auth/admin.directory.orgunit.readonly
Do users sync automatically on a regular schedule?
Yes, users are synced from your Google Workspace account to Verkada Command automatically every 40 minutes.| Field | SCIM Attribute | Schema | Required | Allowed characters |
|---|---|---|---|---|
| Email address (username) | userName | Core | Yes | Valid email address. Maximum 255 characters. |
| First name | name.givenName | Core | Yes | Supports letters, numbers, spaces, & ' - . , ( ) /. Maximum 100 characters. |
| Last name | name.familyName | Core | Yes | Supports letters, numbers, spaces, & ' - . , ( ) /. Maximum 100 characters. |
| Middle name | name.middleName | Core | No | Maximum 255 characters. |
| Work phone* | phoneNumbers | Core | No | E.164 format with a country code (e.g., +14155552671) is required for reliable verification. Maximum 32 characters. |
| External ID | externalId | Verkada | No | Supports letters, numbers, _ @ - . +. Maximum 128 characters. |
| Employee title | title | Core | No | Maximum 255 characters. |
| Department | department | Enterprise | No | Maximum 255 characters. |
| Company name | organization | Enterprise | No | Maximum 255 characters. |
| Employee ID | employeeNumber | Enterprise | No | Maximum 255 characters. |
| Department ID | costCenter | Enterprise | No | Maximum 255 characters. |
| Active status | active | Core | No | Supports true or false |
Requires users in your organization to set up and use 2FA when logging in via a password.
Toggle on this enforcement in Admin > Privacy & Security > Authentication & User Management.
| | **Review Session Duration** |Set the amount of time a user’s session lasts before having to log in again.
Review the configured session duration in Admin > Privacy & Security > Session Timeout.
| | [**Set Up and Enable SSO**](https://github.com/verkada/Verkada-Support-Docs/blob/main/en/command/single-sign-on-sso/authentication-and-provisioning-overview.md) |1.
Configure SSO as an authentication method for your users.
2.
Complete the Run Login Test step to enable it (for enhanced security, make SSO required).
| | [**Set Up SCIM**](/command/security/identity-providers/scim-token-management) | Configure SCIM to provision and manage your users and groups through Okta or Microsoft Entra ID identity management. | | [**Add Primary Key Contact**](/command/organization-settings/manage-your-admin-page-settings/manage-contacts) | Add a [primary contact](https://command.verkada.com/admin/org-settings/org-details) who serves as the designated point of contact for general communications. | | [**Add Billing Key Contact**](/command/organization-settings/manage-your-admin-page-settings/manage-contacts) | Add a [billing contact](https://command.verkada.com/admin/org-settings/org-details) who serves as the designated point of contact for billing-related communications. | | [**Add Security Key Contact**](/command/organization-settings/manage-your-admin-page-settings/manage-contacts) | Add a [security contact](https://command.verkada.com/admin/org-settings/org-details) who serves as the designated point of contact for security-related communications. | | **Review Users** | Ensure your [users list](https://command.verkada.com/admin/users) and user roles are up to date and remove any users if necessary. | | [**Review Groups**](/command/users-and-permissions/manage-users-in-your-organization/manage-command-groups) | Ensure each user is added to the [group(s)](https://command.verkada.com/admin/groups) that grants the correct permissions. | | [**Review Default Image and Video Data Location**](/command/security/privacy-and-security-disclosure/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing) |1.
Set the default geographic region where camera video and image data will be stored.
2.
Review the configured location in Admin > Privacy & Security > Data Residency.
| | **Confirm Appropriate Notice** |Confirm that:
All physical sites have appropriate signage with regard to camera recordings.
The company receives appropriate consent from employees and guests.
| | **Review People Analytics Notice** | Review and accept the Analytics Terms and Conditions, found in the **Admin > Cameras > Analytics**. | | [**Review Audit Logs**](/command/organization-settings/manage-your-admin-page-settings/manage-and-view-audit-logs) | Review the [logged actions](https://command.verkada.com/admin/privacy-security/audit-log) of Command users in your organization to check for irregular activity. | | {% endstep %} | | | {% endstepper %} | | *** ## Dismiss an action from the checklist If a specific action does not pertain to your organization, you can dismiss it from the list. Next to the action item, click the checkmark and select **Complete** or **Dismiss**. If it has a dropdown arrow next to the item name, it does not count toward your completion percentage.- Site
- Location
- Schedule Firmware Updates
- Audio
- Low bandwidth mode
- RTSP streaming
- Motion events
- Crowd events
- Data storage location
- Analytics features
- Cloud Backup
- Site
- Location
- Sensors and Triggers
- Notifications
- Site
- Location
- Site
- Location
- Site
User logins
* **User attempted login**: Displays login success or failure, with reason * **User attempted logout**: Displays logout success or logout failure, with reasonVerkada Support access
When a member of the Verkada Support team is granted access by a customer, the event along with the details (time, access window size, and so on) alongside the actions taken by the Support team member (for example, configuration changes) are logged. Notifications can be set for when these actions are taken. * **Support Access**: A Verkada Support team member was granted access to the organization by an Admin user. * **Support Access Granted**: An Admin created or modified a Verkada Support access window. This event occurs when an Admin creates or modifies the duration in which a Verkada Support team member can access the organization.User management
* **Export Users CSV**: User list was exported from this organization * **User Added to Organization**: User was added * **User Removed from Organization**: User was removed * **Users Removed from Organization**: Multiple users were removed * **Organization User Provisioned**: User added by SCIM * **Resent invitation for User to join Organization**: Invitation was sent to an existing user in the org * **User Created**: New user created within the organization * **User Invited**: New user was invited to the organization * **User Login**: User attempted a login * **User Logout**: User logged out * **User Email Modified**: User’s email was changed * **User Employment Modified**: Access user’s employee information was changed * **User Name Modified:** User’s first and/or last name was changed * **User Changed Password**: User changed their password * **User Permissions Modified**: Permissions were modified for a user * **User Roles Modified**: Permissions, including access role permissions, were modified for a user * **User Modified RTSP Credentials**: User made an Real-Time Streaming Protocol (RTSP) change on a camera * **User Preference Set**: User set or changed preferences * **Two-Factor Reset**: Two-factor authentication was reset * **SAML Config Created**: New Security Assertion Markup Language (SAML) configuration was created * **SAML Config Deleted**: SAML configuration was deleted * **SAML IDP Initiated:** SAML identity provider (IDP) was initiated * **SAML Config Updated**: SAML configuration was updated * **SCIM Provider Created**: New System for Cross-domain Identity Management (SCIM) provider created * **SCIM Provider Deleted**: SCIM provider was deleted * **SCIM Provider Modified**: SCIM provider was modified * **SCIM Token Regenerated**: SCIM token has been regenerated * **User Group Action Taken**: User group has been created, modified, or deleted * **Users Removed from Organization**: User or set of users were removed from the organization * **Force Logout Requested**: Admin force logged out a userOrganization, site, and group actions
* **Organization Modified**: Organization renamed in Verkada Command * **Organization Property Modified**: Property or setting of the organization was modified * **Site Action Taken**: Site has been created, modified, or deleted * **Webhook Toggled**: Webhooks were enabled or disabled * **API Key Modified**: API key was created or modifiedDevice management
* **Devices Installed**: User added a new device to Command * **Devices Uninstalled**: User removed a device from Command * **Device Remotely Accessed**: Support accessed this device * **License Claim Event**: License key was added to the organization * **License Grant Event**: Additional licensing was added to the organization by Verkada * **Override Trial Event**: Verkada added more days to this organization’s trial * **Viewing Station Grid Updated**: Change was made to a Viewing StationCamera events
* **Archive Action Taken**: User created, modified, or deleted a video archive * **Camera Config Modified**: User modified a camera configuration. See details for which configuration * **Profile Image Downloaded**: User downloaded still image from camera footage * **Profile Image Uploaded**: User uploaded an image into a profile * **Profile Results Searched By Identity**: Profile was used for people search * **Profile Photo Added:** User added a people profile photo * **Profile Created**: User created and named a people profile in Command * **Profile Deleted**: People profile was deleted * **Profile Viewed**: User viewed a profile/person * **Profile Merged**: User merged two profiles/people into a single profile * **Profile Unmerged**: User unmerged a profile * **Profile Updated**: User updated a profile * **Profile Searched**: User searched for a profile/person * **Profile Searched with Details**: User searched for a profile/person with attributes included * **Profile Details Viewed**: User viewed details of a profile/person * **Profile Searched by Uploading Image**: User uploaded an image to perform a search in Command * **Profile Suggestions Viewed**: Suggested profiles/people were viewed by a user * **Profile Suggestions Updated**: Suggested profiles/people were updated * **Vehicle Searched**: A user searched for a vehicle * **History Viewed:** User viewed historical video * **Live Stream Started**: User started a live video stream * **Embed Link Created**: User created a video embed link * **Live Link Created**: User created a shareable link * **Timelapse Action Taken**: User created, modified, deleted, or downloaded a video time lapse * **Camera Retention Settings Updated**: A camera’s retention was changed * **Camera Site Changed**: A camera site was modified * **Helix Event Modified**: A helix event change was made through API * **Video Sharing Agreement Updated**: Video sharing policy agreement has been changed. * **Shared resource created**: An archive was sharedAccess events
* **Access Alert Modified:** Access alert-related change was made * **Aux Input Modified**: AUX input-related changed was made * **Door Created**: New access door was created * **Door Deleted**: Access door was deleted * **Door Modified**: Change was made on an access door * **Door Moved**: Door’s settings was moved to another door port * **Elevator Modified**: Elevator-related changed was made * **Access Group User Added**: User was added to an access group * **Access Group Created**: New group was created for access * **Access Group User Removed**: User was removed from an access group * **Access Level Modified**: Access level-related change was made * **Access Lockdown Modified**: Lockdown was modified * **Access Muster Report Modified**: Roll call report was ran * **Access Muster Template Modified**: Roll call template related changed was made * **Access Device nearby Camera Modified**: Door’s camera was changed * **Access Org Badge Template Modified**: Badge template-related change was made * **Access Schedule Created**: User created an access schedule * **Access Schedule Deleted**: User deleted an access schedule * **Access Schedule Modified**: User modified an access schedule * **Access Site Config Modified**: Access site-related change was made * **Access Device Moved**: Access controller was moved to a different site * **Access Method Added**: New method (badge, Bluetooth, and so on) of unlocking a door was added to a user * **Access Method Removed**: Method of unlocking a door was removed from a user * **Access Method Modified**: Method of unlocking a door was modified in a user * **Access Roles Granted**: User granted access roles * **Access Roles Revoked**: User revoked access roles * **Access Users Exported**: User exported Access user list * **Access Org Config Modified**: An access organization setting was changedAlarm events
* **Alarm Settings Modified:** An alarm related change was madeSensor events
* S**ensor Alert Config Modified**: Change was made on a sensor alert * **Sensor Calibration**: Sensor calibration-related event was made on the org (calibrating a sensor reading and/or generation of a certificate) * **Sensor Config Modified**: Change was made on an air quality sensor * **Sensor Dashboard Modified**: Change was made on an air quality dashboard * **Sensor Device Details Modified**: Air quality sensor’s name, location, and so on was changed * **Sensor Site Changed**: Air quality sensor was moved to another siteWill my bookmarks still work?
Yes, any links to command.verkada.com will automatically redirect to your organization’s subdomain login page.Does this change how I log in?
No, your login credentials and authentication process remain the same—only the URL is different.What if I manage multiple organizations?
Each organization has a unique subdomain to make it easier to navigate between them. Users can bookmark multiple subdomains for quick access.Does this impact security?
No, this is strictly a change to the login experience. All existing security measures, including SSO and multi-factor authentication (MFA), remain the same.One door license per door on:
AC62
AC42
AC41
AC12
AX11 IO Controller: One access IO controller license per controller
Mobile NFC: One mobile NFC credentials license per 20 users
| | Alarms |One alarm license per location (physical address). Alarm licensing covers a limited number of devices and video verification events.
In addition, one license per device for the following:
BZ11 Horn speaker
Cellular backup module
Learn more about each alarm license each tier offered.
| | Cameras |One camera license per Verkada camera
One camera license per non-Verkada camera (channel) connected to a Command Connector
Optional: One Cloud Backup License per 30-day increments on a single device’s cloud retention. Learn more about Extended Cloud Backup Licensing.
| | Multisensor cameras |One MLT2 camera license per two-camera multisensor
One MLT4 camera license per four-camera multisensor
| | Environmental sensors | One sensor license per environmental sensor | | Gateway |One cellular gateway license per cellular gateway
One Wi-Fi gateway license per Wi-Fi gateway
Optional: One data plan license per connected camera or intercom. A multisensor camera needs four data licenses.
| | Intercom |One Intercom license per intercom device
One Desk Station license per iPad running the Verkada Desk Station app
| | Viewing station | One viewing station license per viewing station | | Workplace | One Workplace license grants you access to use one Guest iPad and one Mailroom site. | *** ## Purchase Command licenses {% hint style="warning" %} Command licenses are available in 1, 3, 5, and 10-year terms. {% endhint %} There are two types of licenses: capacity increase (CAP) and renewal (RNW). * **Capacity Increase (CAP) licenses**: Verkada CAP licenses are automatically activated when the associated Verkada hardware order is shipped. New device licenses include a 30-day extension beyond the purchased term to accommodate shipping and installation. The extension period is fixed and does not depend on when the device is installed or activated. * **Renewal (RNW) licenses:** Verkada RNW licenses extend an organization’s existing term but remain inactive until the earlier of: * The date they are claimed within a Command organization or * One year after the purchase date. If unclaimed after one year, the license automatically activates, and its term begins to run. Any license claimed beyond this one-year period results in a shortened remaining term. This policy ensures compliance with the intended service period. Licenses are usually sold with your Verkada devices, but you can also purchase them separately from your Verkada reseller or sales representative. See the latest [licensing prices](https://www.verkada.com/pricing/). *** ## Renew your licenses When your licenses are soon to expire, you need to renew your license to avoid losing access to Verkada Command. You can renew your license by contacting your Verkada Sales Representative or your Verkada Reseller. ### Renewal notifications and license expiration 30 days before expiry, you will expect to: * Receive an email notifying you that your licenses are about to expire. * See a banner in Command. {% hint style="danger" %} You will lose access to Command if you haven’t renewed your license within 30 days after your expiration date. {% endhint %} *** ## Licensing overcap policy An organization is considered to be in overcap when it has more devices commissioned than the number of licenses claimed. ### Overcap policy Verkada enforces software compliance by requiring each hardware product to have a valid, claimed software license(see requirements above). The Overcap policy introduces an **Invalid** status for organizations that exceed their claimed licenses, ensuring compliance across all Verkada products. After a 90-day grace period, organizations without proper licensing lose access to critical functions, including device management and notifications. ### How it works Verkada will notify all Command users 90 days **before** an organization loses access, prompting them to claim additional licenses. Organization Admins will receive in-product banners and emails over 90 days to ensure they restore compliance. {% hint style="danger" %} All devices will remain functional when access to Command is restricted. However, users will still have access to the **License Manager**, **Devices**, and **Technical Support** pages when an organization is no longer compliant. {% endhint %} ### Restore compliance Organization Admins can perform **one** of the following actions to restore compliance: * Claim any unused licensing keys. * Remove any unused devices from the organization. * Contact your Sales Representative or emailWhat happens if I have insufficient or expired licenses?
Verkada will send you an email notification and add a banner notification to your Command Organization. You need valid licenses to use Command. If you don’t [claim your licenses](/command/licensing/manage-your-licenses/find-and-add-license-keys-to-command) when adding new devices or products or renew them when they expire, you will lose access to most of your Command functionality after a 30-day grace period. * For expired organizations, you have a 30-day grace period before you lose access. * For organizations with insufficient licenses, you have a 90-day grace period before you lose access. * Contact your Verkada Partner or Sales Representative to purchase additional licenses. At the end of this grace period, you will no longer have access to any of your devices or configure any settings. Alarms and Event notifications will also be disabled. You will, however, be able to delete devices and products so you get back into compliance in case you have insufficient licenses.How will I know if my licenses are soon to expire?
30 days before your license is set to expire, Verkada will send you an email notification and add a banner notification to your Command Organization.How do I regain full access to Command?
If your access to Command was limited due to insufficient licenses, you can: * Delete the products that are above your license cap to get back into compliance * Contact your Verkada Partner or Sales Representative to purchase additional licenses. If your access to Command was limited due to expired licenses, you can contact your Verkada Partner or Sales Representative to renew your licenses.Will my devices still record data?
As long as your Verkada devices are still connected, they will continue to record data. This data will be available when you regain access to Command (as long as you’re still within the retention period for the given device). Badges and Verkada Pass will still work as before, but you’ll be unable to change your settings via Command.What happens if I don’t return my expired trial devices?
Trialing a Verkada device is the best way to experience how our products and platform works. You can initiate a free trial for most of our devices through your Verkada Sales Rep, or your Verkada Partner. The free trial lasts for 30 days. After the 30 days are up, you’ll see a banner in Command reminding you to return or purchase your trial devices. If you don’t return the devices within 30 days of the expiry date they will stop working as expected. If you need additional time to test our trial devices and platform, you can ask your Verkada Sales Rep for an extension.Can a site be assigned to multiple license groups?
No. Each site can be assigned to only one license group at a time, but a license group can include multiple sites.Can I remove a license key from a group?
You can’t fully remove a license key from a group, but you can reassign it to a different license group at any time.What happens if I move a site without transferring its corresponding licenses?
Devices move with the site, updating device counts in the license groups. Licenses remain in the original license group until moved manually, so you must transfer license keys to maintain compliance.What if I did not receive an order email?
If you did not receive an order email from Verkada with the license key, we recommend that you: * Check your spam folder: Sometimes, the order email might be sent to your spam folder. * Ask the person who ordered the cameras: If the order was placed by someone else in your organization, they might have received the order email. * Ask your Verkada reseller: If your Verkada reseller handled the order, they might have received the order email.What do I do if I am unable to locate the order email?
If you or your reseller are unable to locate the order email, contact [Verkada Support](/command/need-help/contact-verkada-support). **What happens if I don’t claim my license?** If you don’t claim your license after adding new products to Command, you’ll see a banner reminding you to claim your license key. All organization admins will also receive an email reminder to claim the license key after 5 days. If you don’t claim your license keys within 36 days of adding the new products, you’ll lose access to Command.What happens if I have multiple product types?
Verkada licenses are co-termed **to a single expiration date even if you have multiple product types**. The combined expiration date is still the weighted average of the individual licenses claimed into that organization. Each product is weighted by the MSRP of the license cost for that product. For example, if an organization has 2 licenses: * One 1-year (365 days) camera license * One 3-year (1095 days) air quality sensor license Because the camera license MSRP is US$199 and the air quality sensor license MSRP is US$249, the co-termination date would be calculated as: ((365\*3\*249) + (365\*1\*199)) / ((1\*249) + (1\*199)) = 771 days Assuming the 2 licenses were bought on the same day, the co-term expiration date would be 771 days from the start of the license. If you compare that to the 730 days in the camera-only example above, you see that the co-term expiration date is at a future time. This is because Verkada Air Quality Sensor licenses are more expensive than camera licenses and, therefore, are given more weight in the co-term calculation.What happens if I add devices in the middle of my license term?
Verkada sells 1, 3, 5, and 10-year licenses. When you add a license to an existing organization, the co-terminating expiration date is extended for all of your devices, accordingly. **Example scenario**: You originally purchased 10 x 1-year camera licenses. Upon purchase, you have 10\*12 = 120 camera months. 120 camera-months / 10 cameras = 12 remaining months 4 months into the license term, you decide to purchase 3 x 1-year camera licenses. Immediately prior to purchase, you have 10\*8=80 camera months. 80 camera-months / 10 cameras = 8 remaining months After purchase, you have extra credit of 3\*12=36 camera months for a total of 80+36=116 camera months. Verkada automatically applies those 36 camera months for your new 13 camera organization. 116 camera-months / 13 cameras = 8.92 remaining months So with this new purchase, your organization’s expiration date moved forward by 0.92 months. In this way, your organization only has a single co-terminating expiration date, avoiding the confusion associated with multiple expiration dates.What if I want to manage multiple license renewal dates for my org?
You can create license groups to organize licenses and devices by site, region, or cost center, providing flexibility, improved visibility, and easier administration. Each group has its own renewal date and license capacity while remaining part of the same Command organization. {% hint style="warning" %} See [License Groups](/command/licensing/manage-your-licenses/license-groups) for more information. {% endhint %}What happens if I claim a license key as renewal?
When you claim a license key as a renewal, your overall expiration date will be extended based on the proportion of the renewal license purchased. Before February 2025, renewal licenses appeared in a separate "Renewed" tab under License Manager, and Cellular Data Plan licenses were managed in a separate table in license manager with its own renewal date. Starting in February 2025, the two renewal dates and products will be merged into a single date and table in the License Manager. This may update your licensing terms once these merge into a single, organization-wide renewal date.Dome series
CF81-E
CM41
CM41-E
CM41-S
CH52-E
Bullet series (1st and 2nd generation)
AC42
TD52
BP41
BH51
BK21
BK11
BC82
| | 10/100/1000 Mbps |CB63-E
CB53-E
CD63
CD63-E
CD53
CD53-E
CD43
CD43-E
CF83-E
CM22
CM42
CM42-S
CY53-E
Pan-Tilt-Zoom series
SV11
SV20 series
AC41
| | 100/1000 Mbps |AX11
AC62
BZ11
| | 1000 Mbps | VX52 | # Clear Your Browser Cache Learn how to clear your browser’s cache If you encounter isolated, unusual behaviors while using Verkada Command, it can sometimes be due to a particular browser, and you can fix it by clearing your browser cache. *** ## Chrome {% stepper %} {% step %} **Go to** [**https://command.verkada.com**](https://command.verkada.com)**.** {% endstep %} {% step %} **On the left of the URL bar, click the Site Controls icon.** {% endstep %} {% step %} **Click the dropdown and select Site settings > Delete data.** {% endstep %} {% step %} **Click Delete.** {% endstep %} {% endstepper %} ## Firefox {% stepper %} {% step %} **Go to** [**https://command.verkada.com**](https://command.verkada.com)**.** {% endstep %} {% step %} **On the left of the URL bar, click the lock icon.** {% endstep %} {% step %} **Click Clear Cookies and Site data > command.verkada.com.** {% endstep %} {% step %} **Click Remove.** {% endstep %} {% endstepper %} ## Safari {% stepper %} {% step %} **Click Safari > Preferences > Privacy.** {% endstep %} {% step %} **Click Manage Website Data.** {% endstep %} {% step %} **Scroll down and select verkada.com.** {% endstep %} {% step %} **Click Remove.** {% endstep %} {% endstepper %} ## Edge {% hint style="warning" %} Please make sure you’re running the [latest version](https://www.microsoft.com/en-us/edge). {% endhint %} {% stepper %} {% step %} **Go to** [**https://command.verkada.com**](https://command.verkada.com)**.** {% endstep %} {% step %} **On the left of the URL bar, click the lock icon.** {% endstep %} {% step %} **Click Cookies.** {% endstep %} {% step %} **Click Remove until all cookies have been deleted.** {% endstep %} {% endstepper %} # Verkada Command Account FAQ Learn about the common questions asked for your Verkada Command account ## Command user accountsCan an Org Amin unlock user accounts?
Org Admins do not have the ability to unlock users who have been locked out.Can Verkada Support unlock user accounts?
Verkada Support does not have the ability to unlock user accounts. Users must wait the full 15 minutes before they can attempt to log in again.How can I access a user’s Command account who is no longer with the company or organization?
You need access to that user’s mailbox or add their email address as an alias to your mailbox. Once you have access to their mailbox, request to reset the password to get a password reset link via email. With the password reset link, you can reset the password to their account and log in.How many failed login attempts does Command allow before a user gets locked out?
User accounts are locked out after 7 failed attempts.How long is the lockout period?
The lockout period is 15 minutes.How long does the Verkada new account activation link email last before it expires?
The Verkada new account activation link expires 30 days after the email invite is sent and can only be clicked once.How long does a Verkada password reset link email last before it expires?
The password reset link email expires after 24 hours.Is 2FA required for Org Admins?
Yes. Two-Factor Authentication (2FA) is required for all Org Admins in Command. If not already configured, Org Admins will be prompted to set it up at their next login. This requirement cannot be bypassed.Can an Org Admin disable 2FA for another user’s account?
Yes, they can. Follow the steps outlined in [Activate 2FA for Your Command Account.](https://github.com/verkada/Verkada-Support-Docs/blob/main/en/command/users-and-permissions/enable-2fa-for-your-command-account.md)Can Verkada Support disable 2FA for a user account?
Verkada Support does not have the ability to disable 2FA for a user.How do I change or reset my password?
In Verkada Command, at the bottom left, click the organization where you want to change your password.On the slide-out page, click My Account.Under Security > Password, click Change.a. Enter your current password.\ b. Enter your new password twice.\ c. Click Change to confirm.Alternatively, use the password reset link, enter your email address, and click Reset via Email.Can Org Admins reset a user’s password?
Yes, Org Admins can reset Command users’ passwords. In Verkada Command, go to All Products > Admin.Under Org Settings > Users, select the user whose password you wish to reset.Click on the three dots next to the user’s name and click on Control Login.Click Reset Password. This will log the user out of all existing Command sessions and send them a link via email to reset their password.What is the URL to reset a password?
The password reset URL isCan Verkada Support set a user’s password?
Verkada Support does not have the ability to set user passwords.What is the Verkada password complexity requirement?
The password must be at least 8 characters, contain one number (0 to 9) and at least one special character; for example, !@#$%&.What email address do password resets and user invites come from?
The email address isWhat is the password reuse policy for Command users?
Users cannot reuse any of the last 30 passwords that have been used.Does Verkada enforce a maximum password age?
By default, Verkada does not enforce a maximum password age. To enforce this policy, integrate Verkada with SSO or Active Directory through SAML, where password age requirements can be configured.What does it mean if a password was detected in a "data leak"
Credential stuffing is when attackers use passwords leaked in other data breaches to try to access your account. To keep you safe, Verkada checks every new password against [Have I Been Pwned (HIBP)](https://haveibeenpwned.com/Passwords) — a trusted database of exposed passwords. If your chosen password appears in this database, Verkada will block it and prompt you to select a stronger one. For best security, use a randomly generated password. **How it works** Your actual password never leaves Verkada.We create a SHA-1 hash of your password and send only the first 5 characters of that hash to HIBP.HIBP returns a list of possible matches.Verkada checks locally to see if your password is compromised without revealing your password or email address to anyone. This process keeps your account secure while ensuring your password stays private.
.
{% endstep %}
{% step %}
The overview page displays information:
1. Licensing:
* Detailed product breakdown of licensing for that customer's organization, including any specific licenses that may be missing
* When a customer’s license is set to expire, enabling them to proactively reach out about renewals
2. Support cases:
* Active support cases for that organization
* History of cases closed over the past six months
* Support cases and insight into the types of issues and support assistance commonly required by the customer
3. Sales Representative:
* Name and contact information
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Only support cases initiated through Command live chat are shown.
{% endhint %}
***
## Best practice considerations
### Stage devices and sites
* You can [add devices](/command/organization-settings/add-a-device-to-your-command-organization) to an organization before they are physically on-site once you have the order number. This stages all devices from the order in the unassigned sites section for setup and configuration.
* If you have the floorplans and information planned out, you do have the ability to create sites and subsites and assign the devices to the sites so the installer only has to physically install and wire up the device [Manage Your Sites and Subsites | Verkada Help Center](/verkada-cameras/configuration/manage-sites-and-subsites)
### Access for installers
* You should add the installer to the customer Command organization before they go onsite to install the devices. We recommend adding installers as [temporary users](/command/users-and-permissions/manage-users-in-your-organization/manage-temporary-users) and setting an expiration date for their account access.
* Installers should plug-in devices in a staging environment before final installation to verify they come online, register, and check for firmware updates. This ensures quick installation in cases involving ladders, lifts, or other challenging scenarios.
* Installers should download the Command mobile app to assist with viewing cameras during installation. The app eliminates the need for a laptop or repeatedly climbing a ladder to check the camera angle on a desktop.
### Post-installation considerations
* Confirm with the customer if they want to keep the partner accounts as admins, reduce access permissions, or remove the accounts altogether. See [Manage Users in Your Organization](/command/users-and-permissions/manage-users-in-your-organization) for more information.
* Verkada uses [API keys](https://apidocs.verkada.com/reference/introduction) to allow customers to extract data for further analysis. Discuss with the customer if there are any managed services for alerting or reporting they would like integrated with Command.
# End-of-Sale Products
Learn the guidelines for the support availability throughout the life of a Verkada product
The Verkada Lifecycle Policy covers products and services across the portfolio that require ongoing support to remain functional and secure.
To keep pace with changing market demands, Verkada will continuously introduce functionally superior products to replace mature product lines in service.
Our life cycle policy is designed to support you as you transition from one product to the next. We are committed to keeping you informed by communicating key milestones.
***
## End-of-Sale product announcements
| Product | Announcement | End-of-Sale Date | End-of-Support Date |
| ---------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------------------------- | ------------------- |
| [AC42](/command/need-help/end-of-sale-products-policy-overview/ac42) | May 8, 2026 | August 6, 2026 | August 6, 2036 |
| [CB62](/command/need-help/end-of-sale-products-policy-overview/cb62) | May 7, 2026 | August 5, 2026 | August 5, 2036 |
| [CB52](/command/need-help/end-of-sale-products-policy-overview/cb52) | May 7, 2026 | August 5, 2026 | August 5, 2036 |
| [Classic Alarms (Canada)](/command/need-help/end-of-sale-products-policy-overview/classic-alarms-canada) | February 12, 2026 | March 15, 2026 | |
| [BR31 (US/CA)](/command/need-help/end-of-sale-products-policy-overview/br31-and-br32-us-ca) | February 12, 2026 | March 15, 2026 | |
| [BR32 (US/CA)](/command/need-help/end-of-sale-products-policy-overview/br31-and-br32-us-ca) | February 12, 2026 | March 15, 2026 | |
| [CH52-E](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-ch52-e) | November 4, 2025 | February 1, 2026 | February 1, 2036 |
| [CD42-F](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd42-f-cd52-f) | August 15, 2025 | August 15, 2025 | August 15, 2035 |
| [CD52-F](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd42-f-cd52-f) | August 15, 2025 | August 15, 2025 | August 15, 2035 |
| [ACCX-TBL-2](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-accx-tbl-2) | June 24, 2025 | September 22, 2025 | |
| [CD42](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd42-cd52) | May 1, 2025 | July 31, 2025 | August 1, 2035 |
| [CD52](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd42-cd52) | May 1, 2025 | July 31, 2025 | August 1, 2035 |
| [CF81-E](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cf81-e) | May 1, 2025 | July 31, 2025 | August 1, 2035 |
| [AD33](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-ad33) | May 1, 2025 | July 31, 2025 | August 1, 2035 |
| [CD62](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd62) | February 5, 2025 | May 1, 2025 | May 1, 2035 |
| [TD52](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-td52) | November 11, 2024 | February 1, 2025 | February 1, 2035 |
| [ACCX-TBL-1](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-accx-tbl-1) | November 11, 2024 | February 9, 2025 | |
| [BR34](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-br34-wireless-glass-break-sensor) | November 7, 2024 | February 7, 2025 | |
| [Classic Alarms (US)](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-classic-alarms-us-only) | November 7, 2024 | February 7, 2025 (US only) | |
| [CM41-S](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cm41-s) | November 6, 2024 | February 1, 2025 | February 1, 2035 |
| [AC41](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-ac41) | June 4, 2024 | July 31, 2024 | July 31, 2034 |
| [CM41](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cm41) | June 8, 2023 | August 31, 2023 | August 31, 2033 |
| [BC51](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-bc51) | June 8, 2023 | August 31, 2023 | August 31, 2033 |
| [AD32](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-ad32) | May 4, 2023 | May 5, 2023 | May 5, 2033 |
| [CB51](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cb51-cb61) | February 16, 2023 | May 20, 2023 | May 20, 2033 |
| [CB61](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cb51-cb61) | February 16, 2023 | May 20, 2023 | May 20, 2033 |
| [SV11](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-sv11) | December 14, 2022 | March 1, 2023 | March 1, 2033 |
| [CM61](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-d30-cm61) | March 31, 2022 | June 30, 2022 | June 30, 2032 |
| [D30](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-d30-cm61) | March 31, 2022 | June 30, 2022 | June 30, 2032 |
| [AD31](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-ad31) | March 21, 2022 | April 30, 2022 | April 30, 2032 |
| [CD41](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd41) | January 25, 2022 | February 25, 2022 | February 25, 2032 |
| [D80](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-d40-d80) | December 31, 2021 | January 31, 2022 | January 31, 2032 |
| [D40](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-d40-d80) | December 31, 2021 | January 31, 2022 | January 31, 2032 |
| [CD51](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd51-and-cd61) | December 30, 2021 | January 30, 2022 | January 30, 2032 |
| [CD61](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-cd51-and-cd61) | August 30, 2021 | September 30, 2021 | September 30, 2031 |
| [D50](/command/need-help/end-of-sale-products-policy-overview/end-of-sale-announcement-for-d50) | April 1, 2020 | May 1, 2020 | May 1, 2030 |
***
## Key milestones
{% hint style="info" %}
**Key definitions**
* [**End-of-Sale announcement**](#h_91f1fc51eb) **(this article)**: Official End-of-Sales notice.
* [**End-of-Sale date**](#h_68a382d03d): The last date to order the product through Verkada.
* [**End-of-Support date**](#h_6516b0503b): The last date a product will be supported by Verkada.
{% endhint %}
### End-of-Sale announcement
Date of official end-of-sale notice, typically one (1) month prior to the last order date. Products being discontinued will be announced as end-of-sale and identified on the [Verkada Updates](https://www.verkada.com/updates/) webpage.
### End-of-Sale date
The last date to order the product through a Verkada-authorized reseller. Discontinued products are removed from the [Pricing](https://www.verkada.com/pricing/) webpage and are no longer available for purchase. Device-specific licenses corresponding to discontinued hardware products will remain available after the end-of-sale date unless otherwise specified in the announcement. After the end-of-sale date, Verkada will continue to support the discontinued product until the end-of-support date. Verkada typically provides support for a given product for a period of ten (10) years after the end-of-sale date.
### End-of-Support date
The last date a product will be supported by Verkada, generally up to ten (10) years after the end-of-sale date. After the end-of-support date, Verkada will no longer:
* Guarantee the legacy product will be able to connect or remain indefinitely compatible with the management platform, Verkada Command
* Provide Technical Support for troubleshooting
* Issue firmware updates or automatic patches for the hardware
* Ensure new software features available through the management platform, Command, are compatible with the hardware or the firmware running on it
{% hint style="warning" %}
**\*** If these situations occur, [Verkada Support](/command/need-help/contact-verkada-support) will do its best to provide a workable solution.
{% endhint %}
***
## FAQ
Can customers return a discontinued product that they purchased prior to the end-of-sale date?
Customers may return any product *within 30 days of purchase*.What happens if a discontinued product under warranty needs to be replaced?
Verkada will replace return merchandise authorization (RMA) units with the same discontinued product. If the discontinued product is no longer available for replacement, Verkada will replace the discontinued product with functionally equivalent hardware, and transfer the remaining license term to the replacement hardware.What if a customer upgrades their legacy hardware to newer hardware?
Verkada will transfer the remaining value of any licenses attributable to the legacy hardware for use with the new updated hardware the customer purchased.What if Verkada no longer is able to offer the Cloud Service?
Under our End User Agreement, Verkada gives our customers a license to use Verkada’s software. Without the software, customers will have limited or no access to their data, Verkada’s product features and Verkada’s Software, and Verkada’s hardware will not function as designed. However, in the event of Verkada’s dissolution, winding up, or other inability to continue providing its software to its customers, upon written request from a customer, Verkada will update the firmware on the ***camera*** hardware that the customer purchased in order to support RTSP streaming on a commercially reasonable timeline.What does this mean?
As of August 6, 2026, we will no longer sell AC42 SKUs. However, we will continue to provide support for the product through our 10-year warranty period.Can customers return products that they purchased?
Customers can return products *within 30 days of purchase*.What happens if a product under warranty needs to be replaced?
We will replace RMA units with the same model, if available. Otherwise, we will replace them with the next most similar product.What does this mean?
As of August 5, 2026, we will no longer sell CB62 SKUs. However, we will continue to provide support for the product through our 10-year warranty period.Can customers return products that they purchased?
Customers can return products *within 30 days of purchase*.What happens if a product under warranty needs to be replaced?
We will replace RMA units with the same model, if available. Otherwise, we will replace them with the next most similar product.What does this mean?
As of August 5, 2026, we will no longer sell CB52 SKUs. However, we will continue to provide support for the product through our 10-year warranty period.Can customers return products that they purchased?
Customers can return products *within 30 days of purchase*.What happens if a product under warranty needs to be replaced?
We will replace RMA units with the same model, if available. Otherwise, we will replace them with the next most similar product.| SKU | Description |
| LIC-BB-1Y-CAP | 1-Year Basic Alarms License (Classic Alarms), Capacity Increase |
| LIC-BB-3Y-CAP | 3-Year Basic Alarms License (Classic Alarms), Capacity Increase |
| LIC-BB-5Y-CAP | 5-Year Basic Alarms License (Classic Alarms), Capacity Increase |
| LIC-BB-10Y-CAP | 10-Year Basic Alarms License (Classic Alarms), Capacity Increase |
| LIC-BA-1Y-CAP | 1-Year Standard Alarms License (Classic Alarms), Capacity Increase |
| LIC-BA-3Y-CAP | 3-Year Standard Alarms License (Classic Alarms), Capacity Increase |
| LIC-BA-5Y-CAP | 5-Year Standard Alarms License (Classic Alarms), Capacity Increase |
| LIC-BA-10Y-CAP | 10-Year Standard Alarms License (Classic Alarms), Capacity Increase |
| SKU | Description |
| LIC-BX-MB-1Y-CAP | 1-Year Basic Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MB-3Y-CAP | 3-Year Basic Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MB-5Y-CAP | 5-Year Basic Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MB-10Y-CAP | 10-Year Basic Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MA-1Y-CAP | 1-Year Advanced Video Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MA-3Y-CAP | 3-Year Advanced Video Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MA-5Y-CAP | 5-Year Advanced Video Alarms License (New Alarms), Capacity Increase |
| LIC-BX-MA-10Y-CAP | 10-Year Advanced Video Alarms License (New Alarms), Capacity Increase |