We’re adding an option on the Account Settings page that redirects users to the email preferences page of the Verkada website where they can set their communication preferences. This allows users to easily choose what emails they want to subscribe to.

To give Org Admins more visibility into the state of Command users invited to join the organization, we are introducing an "Invited" user state — wherein newly invited users will remain until they accept their invite to Command. Introducing this intermediate state also allows individual users to have more visibility and agency in the process of being added as Command users.

Beginning April 12, Command Organization Admins will be prompted to set up Multi-Factor Authentication (MFA) upon logging in, to provide an added layer of security. Setting up MFA can initially be skipped, but must be completed by July 1, 2024.

A new feature, alert throttling, will limit the number of messages a Command user can receive in a single day to 500. This will help users avoid receiving too many notifications, which can negatively affect their experience using Command.

U.S. government organizations are now able to use Verkada Command hosted in AWS GovCloud. This allows them to use Verkada’s secure cloud solutions on top of the additional security controls provided by AWS GovCloud, such as continuous monitoring of the system, FIPS encryption in transit and at rest, and strengthened session and identity management capabilities.

Command in AWS GovCloud initially supports our FIPS-validated camera models and Verkada Guest, and is available on both web and mobile. Access is limited to government organizations in the United States.

To learn more, read the full announcement.

Org Admins can now set more granular policies such as maximum session duration, idle timeout, maximum concurrent sessions, and maximum login attempts. These policies help customers protect user data, prevent unauthorized access, and mitigate session-related vulnerabilities.

Please refer to this knowledge base article for more details.

Customers can now create temporary user accounts in Command for installers, contractors, and staff. Temporary users can be assigned any role within Command, such as Site Admin or Org Admin, but only for a predetermined time period. Regardless of their assigned roles, temporary users are not able to export information, accept terms and conditions, or create support tokens on behalf of the organization.

Please refer to this knowledge base article for more details.

Users can now log into Command on both mobile and web with a fingerprint, a face scan, or security key. Compared to passwords, these methods are both simpler and more secure, and they’re resistant to online attacks like phishing. With passkeys, users can sign in without even typing in their email or organization name, allowing them to access Command faster in case of an emergency. Org Admins have the option to enable or disable passkey login for all Command users.

Please refer to this knowledge base article for more details.

The new alert creation flow allows users to configure notifications faster through a workflow that is both more intuitive and consistent across alert types and product categories. And to make alerts even more actionable, we’ve added the ability to set up automated responses such as a talkdown on a BZ11 horn speaker. 

To learn more, read the full announcement.

The new Command mobile app makes it easy to navigate across product categories and large deployments. Users can now quickly access different products through an easy-to-reach product menu. The device-level UI is both intuitive and consistent with the web version, allowing users to conduct investigations on the go without any friction or learning curve.