Check Persona Mode and exception limits before migrating IN120 or IN220 locks

Resolve unsupported exception workflows before migrating these locks, and preserve the configuration needed for reclaim.

Source facts

Verkada’s IN120/IN220 integration uses an ASSA ABLOY Door Service Router and Lock Configuration Tool. The guide says LCT does not need to run on the same Windows computer as DSR. It requires Persona Mode for full functionality and warns that features such as Double Badge may otherwise behave incorrectly. The documented integration does not support door exceptions on these models. Moving a door to another site requires removing it from the current site and reclaiming it through the DSR workflow.

Source: Verkada Help — Assa Abloy IN120/IN220 Setup.

Applicability

Applies to ASSA ABLOY IN120 and IN220 locks integrated through the documented Verkada DSR path. Do not apply capabilities from wired doors or other wireless lock families to these models.

DSE recommendation

DSE recommends checking the lock mode and supported exception behavior before approving a migration design. List any holiday, temporary-access, or event workflow that depends on an exception and resolve unsupported requirements before cutover. Keep the DSR and LCT ownership documented even when they run on separate computers. Schedule site moves as coordinated reclaims and preserve the original site and lock configuration for troubleshooting rather than assuming the door can simply be dragged between sites.

Verification

On an approved pilot lock, confirm Persona Mode and exercise the required supported operations. Inspect whether the project relies on an unsupported exception and document the chosen alternative with the owner. For a site move, verify DSR communication and the destination assignment before treating the door as restored to service.

Official reference

Verkada Help — Assa Abloy IN120/IN220 Setup. Reviewed October 15, 2026.