The Pass SDK is for organizations that want Verkada door access inside an app they already own, instead of asking people to install a separate Verkada Pass app. The scenarios below show common ways to use it and which SDK capabilities each one relies on.
The Pass SDK is for organizations that want Verkada door access inside an app they already own, instead of asking people to install a separate Verkada Pass app. The scenarios below show common ways to use it and which SDK capabilities each one relies on.
Migrate to Mobile Credentials
Scenario: A university, or employer already has an app that people carry every day. They want to migrate users from physical credentials to mobile credentials without having to download an additional application.
Hands-free entry in a branded app
Scenario: An employer wants their users to be able to walk up to a Verkada reader and have the door open, with no extra app.
A visible "Unlock" button
Scenario: A building manager or facilities team wants staff or residents to see their doors in a list and unlock one with a tap, for example from a lobby or parking area, reducing resident lockouts or granting remote access.
One app for doors and elevators across sites
Scenario: A campus, hospital, or government facility spans several buildings, and want a single app to show users which doors they have access to and allow for those doors to be unlocked.
Pass SDK or the Verkada Pass app?
| Verkada Pass app | Pass SDK | |
|---|---|---|
| Where the credential lives | In the standalone Verkada Pass app | In your own app |
| Branding and UI | Verkada's | Yours |
| Engineering effort | None | Your team builds the app screens and a small backend |
| Best for | Fast rollout with no development | A single branded app for users |