Customers now have the option to process and store their data, including image and video data, locally in our new Australia-based data center. This will provide organizations with even more control over data residency and data processing. 

With this launch, customers now have three choices for their data processing: the United States, European Union, or Australia. Organizations may still customize their image and video storage location between the US, Canada, EU, or Australia on an org-wide or camera-by-camera basis.

For more details, read the full announcement.

Beginning May 23, customers will be able to manage admin settings in the Command iOS and Android apps for even quicker access to critical features on the go.

Simply tap on Admin at the bottom of the product menu. From here, users can access admin settings such as managing users and groups, creating or editing alerts, adjusting privacy features, and more.

We now support OIDC SSO login for customers using Okta. OIDC, or OpenID Connect, allows the customer to authenticate and authorize via the OAuth 2.0 flow. This means that customers can setup their identity provider and manage their own keys while our backend has zero knowledge of customer data in accordance with our zero trust security architecture.

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.