Admins can select multiple doors within or across sites and make changes to configurations all at once. Admins can use this capability to configure new doors after they have been installed, edit settings for an existing group of doors, and even delete configurations for a group of doors.

For more information, read the full announcement.

Organizations can now “favorite” doors on the Android version of the Verkada Pass app in addition to iOS. Doors marked as “favorite” will show at the top of the door list, regardless of the user’s proximity to that door. This makes it easy for users who frequently use the remote unlock feature of Pass app to quickly find the door they need without scrolling through a list. 

Verkada is announcing the upcoming end-of-sale for the AD33 Mullion Door Reader. Final orders for the AD33 must be received by July 31, 2025.

Learn More

Users can now “favorite” doors on the iOS version of the Verkada Pass app. Doors marked as “favorite” will show at the top of the door list, regardless of the user’s proximity to that door. This makes it easy for users who frequently use the remote unlock feature of Pass app to quickly find the door they need without scrolling through a list. This feature will be available on the Android version of Pass app later this year.

Verkada’s access control solution now supports third-party OSDP door readers, further extending the ability of organizations to integrate their own access control hardware into the Verkada system. OSDP readers can easily be wired to the RS-485 port on any Verkada access controller, and can support your existing credentials.

Atrium is one of the largest campus card management solutions that allows students to have a single student ID card that provides access to campus buildings, carries their meal plan balance, and more. Our new out-of-the-box integration makes it seamless for higher ed organizations using Atrium to automatically sync their users and credentials with Verkada access control. Schools will continue to fully manage their student IDs in Atrium, and any changes will be instantly updated in Command.

Customers were previously able to trigger a lockdown with a wired panic button, but a connection to Command was required for the lockdown to propagate across multiple access controllers. 

Now, access controllers are able to communicate peer-to-peer across the local network, allowing the lockdown to be fully enacted across local access controllers even when internet connectivity is lost. The lockdown response can also include one or more AUX outputs, such as strobes or sirens.

Read the full announcement.

The roll call reports feature is now available to all access control customers. Included with this release from beta is a new integration allowing customers who have both Verkada’s Guest and Access Control solutions to include visitors in their roll call reports. 

Roll call reports let organizations quickly determine who is safe and who is missing in an emergency scenario, such as building evacuations and fire drills. Customers can specify the entrance doors, exit doors / muster points, and people that should be included in a roll call report. Once configured, administrators can run the roll call report to track who is inside a defined area and whether they are marked safe or missing during an emergency.

See the help article to learn more.

Verkada now supports SimonsVoss’s SmartIntego Digital Locking Cylinder and Digital SmartHandle wireless locks. These locks support a variety of access credentials, including ultra-secure, encrypted Verkada DESFire EV3 cards and fobs. These online locks communicate to the SimonsVoss GatewayNode hub, which connects directly to a Verkada AC12 door controller over PoE. Customers can remotely unlock doors, see live door events, manage door schedules and access, trigger a lockdown, monitor battery levels, and more from Command.

SimonsVoss SmartIntego wireless locks on the Verkada platform will be available for customers in the UK and Europe beginning February 13, 2025.

Read the full announcement.

Verkada access control now supports the ability to assign codes solely for the purpose of multi-factor authentication (MFA). These MFA codes can be used alongside a keycard on the AD64 door reader, or third party reader with keypad, to unlock a door when the door is configured in the Card+Code schedule. Since these codes must be used alongside a user’s credential, they do not have to be unique within an organization.

MFA codes are being added in addition to the existing “entry code” field in a user’s profile. A user’s entry code must be unique within the organization. An entry code can be used as a standalone credential when a door is not in a Card+Code schedule, in addition to being used as a second factor when the door is in a Card+Code schedule.