Proof badge data and browser print dimensions before a bulk print run

Proof data ownership, missing-field handling, and actual print alignment before issuing a large badge run.

Source facts

Verkada badge templates can use supported user fields such as name, title, department, and company. User data can be maintained manually, imported by CSV, or synchronized through SCIM. Template management requires the documented Access System Admin role. Printing uses the workstation’s installed printer driver and browser print preview; the guide calls for matching badge dimensions and zero margins. Bulk printing warns when required fields are missing but offers a Print Anyway override, so the warning alone does not prevent incomplete badges.

Source: Verkada Help — Print Access Control Badges.

Applicability

Applies to Verkada Access badge layout and browser printing. A visually printed badge is distinct from the credential’s encoded value and assigned door permissions, which require separate administration.

DSE recommendation

DSE recommends proofing a representative badge before a bulk run. Check long names, missing titles, photos, and the approved organizational branding using controlled test records. Confirm whether SCIM or another source owns each field before making a manual correction that could be overwritten. Restrict use of the missing-data override to an approved exception and reconcile every printed badge with its intended recipient. Store sample files according to the organization’s personal-data handling rules.

Verification

Print a controlled sample using the actual printer, stock, and duplex settings, then inspect alignment and legibility. Confirm missing-field warnings appear on a deliberate test record and stop before bulk printing unresolved records. Compare the final recipient list with the print selection and separately verify credential assignment where required.

Official reference

Verkada Help — Print Access Control Badges. Reviewed October 15, 2026.