Overview

The cleanest way to keep access codes safe is to wire rotation and revoke into the checklists you already run. Two checklist step types do this:

  • rotate_access_codes — generates new codes for every slot on the targeted audience
  • revoke_access_codes — invalidates the pack on the targeted audience

When the checklist step completes, the action runs. No host clicks required.

How it works

Adding a rotation step

  1. Open a checklist template — typically your turnover checklist.
  2. Click Add step.
  3. Pick Rotate access codes as the step type.
  4. Choose the target audience: guest, cleaner, maintenance, or all.
  5. Save the template. Existing in-flight runs of that template will pick up the new step automatically (template-step sync from May 2026).

When a cleaner marks that step complete, the rotation fires. For Igloohome slots, the new PIN is pushed to the lock and read back. For manual slots, the step requires the host to enter the new value before it can complete.

Adding a revoke step

Same flow, with step type Revoke access codes. Useful at:

  • The end of a turnover checklist — guarantees old guest codes can't get back in
  • The end of a check-out checklist — closes the guest pack immediately
  • Inside a maintenance ad-hoc checklist — closes the vendor's window after the job

When the step is required

Both step types support the standard "required for completion" flag. If a turnover checklist has a required rotate step, the run can't be marked complete until the rotation succeeds. This is the recommended setup for production turnovers — it removes the possibility of forgetting.

What if rotation fails?

For smart-lock failures (lock unreachable, API timeout), the step stays pending and shows the error. The run is blocked. Resolve by fixing connectivity or by rotating manually from the Reservation Access page.

For manual rotation, the host gets a textbox; cancelling the dialog leaves the step pending.

Limits and requirements

  • Plan: Rotate and revoke step types are Host and Portfolio.
  • Sequencing: Multiple rotate steps in the same checklist are allowed but only the last one's value persists. Don't chain them unless you have a specific reason.
  • Audit: Every rotation and revoke writes to the slot's audit log with the checklist step id as actor.

FAQ

Can a guest checklist trigger rotation?

No — rotate and revoke are host-side actions. A guest-side checklist step can't fire them. If you want code rotation on a guest action (e.g. "guest reports lost key card"), the host runs the rotation from the Reservation Access page.

What if my cleaner skips the rotation step?

If the step is required, the run can't complete. If it's optional, the run completes and the codes don't rotate. Make it required if your insurance or property policy requires per-stay rotation.

Does revoke delete the codes?

No — revoke invalidates the pack so the codes can't be used and aren't shown anymore. The values remain encrypted on disk until the 30-day redaction window. Audit history is permanent.

Can I rotate before check-in instead of after check-out?

Yes — add the rotate step to your pre-arrival checklist. The new codes will be live before the guest opens their stay portal.