Add the Guest contact-information step before relying on QR door invitations

Check the site-specific Guest Type and contact step before diagnosing a missing visitor QR code as reader failure.

Source facts

Verkada Guest links a Guest Type to a Visit Access Type to issue visitor door permissions. The guide requires a Contact Info step for delivering QR codes, entry codes, or unlock links. QR codes are viewed through the visitor’s post-sign-in link and require a supported intercom or reader path. The site can restrict door access to invited visitors. Global Guest Types cannot be assigned Visit Access Types, so they cannot provision this door access or include visitors in roll call through that integration.

Source: Verkada Help — Door Access for Guests.

Applicability

Applies to site-specific Verkada Guest door-access configuration. This article addresses invitation delivery prerequisites, not a claim that an email invitation itself authorizes every door or replaces local visitor approval.

DSE recommendation

DSE recommends tracing the complete credential-delivery path when a guest reports that a QR code never arrived. Confirm the Guest Type is site-specific, the contact step is present, and the intended Visit Access Type is linked before replacing readers or resending unrelated messages. Have the host approve which visitors may receive door access and whether invitation-only restrictions are needed. Keep visitor-facing instructions consistent with the actual supported credential and entrance.

Verification

Create an approved test visit using a controlled contact address, complete sign-in, and inspect the delivered credential link. Test the intended reader and an unauthorized door. Confirm that a visitor who does not satisfy the configured invitation restriction receives no unintended door access, and record the tested Guest Type.

Official reference

Verkada Help — Door Access for Guests. Reviewed October 15, 2026.