The new door exceptions calendar lets you easily overlay exception events on the normal door schedule, allowing you to create one-off schedule exceptions. It also lets you only make changes to the portion of the door’s normal schedule that you want to adjust, rather than having to re-create that door’s full-day schedule from scratch. Events can also be copied or made to automatically repeat.

Customers can now use our Okta and Entra ID SCIM integrations to automatically tie physical credential information (keycards or fobs) to users in Verkada Command, allowing your SSO provider to serve as the single source of truth. One credential can be synced per user.

A completely new set of access control roles will better support organizations that need to delegate and distribute access control-related responsibilities. Now, permissions can be given by granting roles in three independent categories.

• System roles, which are set at the org level and control things like access control devices, door schedules, and more.

• User roles, which are set at the org level and control things like user groups and credentials.

• Site roles, which grant control over things like access control devices and settings on a per-site basis.

Click here to read the full announcement.

We are launching a new API to automate the syncing of user profile photos from their user system of record. Additionally, for customers that use Verkada as their source of truth for users, we’re introducing an API to download user profile photos so they can be synced to another platform.

Visit our API Documentation page to learn more.

Admins can now more easily use sites to organize their Verkada deployments with access levels that can span multiple sites. 

Click here to learn more about access levels.

As an additional access credential type, Verkada now offers DESFire EV3 encrypted fobs. Like our EV3 cards, these fobs ensure your organization’s data stays secure, while providing a convenient and small form-factor physical access method for your employees.

For more details, see the datasheet.

Introducing our newest fourth-generation door reader, the AD64. Like our recently announced fourth-gen AD34 reader, the AD64 offers improved credential scan performance, Bluetooth Intent Unlock, and premium industrial design. Additionally, this is our first reader that includes a keypad, offering organizations the option to use 6- to 14-digit PIN codes as an additional form of access credential, or as two-factor authentication for added security.

For more details, read our full announcement.

Verkada access control users with Android devices now have the ability to unlock doors using mobile NFC technology. NFC’s short scan range allows for a stable and secure connection. Mobile NFC also allows administrators to choose whether to require that a phone be unlocked before a user is allowed to badge in, creating an additional layer of authentication. Door unlock using Android NFC will be included in the Mobile NFC Credentials license, and is supported by Verkada’s AD33 and newer readers.

For more details, read our full announcement.

In addition to physical and Bluetooth credentials, Verkada now supports mobile NFC credentials via Apple Wallet. With badges in Apple Wallet, employees can simply tap to unlock with their iPhone or Apple Watch.

For added security, organizations can require the mobile device to be unlocked when badging into certain doors, thus leveraging Apple’s powerful security features like Face ID for two-factor authentication. Just like other credential types, badges in Apple Wallet can be easily managed in Verkada Command and synced with SSO providers.

For more details, read the full announcement.

Organizations can now set up automatic deactivation for physical credentials after a set period of inactivity. This can protect against unauthorized access with a lost or stolen credential.

Admins can choose to receive an alert when a credential is auto-deactivated and/or when a deactivated credential is used. They can also view a list of credentials associated with each user and when they were last used.