Overview

An Access Pack is the bundle of credentials a guest, cleaner, or maintenance vendor needs to get into a property — door codes, lock PINs, Wi-Fi, gate codes, alarm codes. Every property has one or more packs. Every reservation gets a pack at booking. Codes rotate on the schedule your checklist defines.

If you previously thought of access as "the door code on the welcome PDF," v4 is a rewrite. Codes are no longer free-form notes. They are first-class records with a lifecycle: created, delivered, rotated, revoked, redacted.

How it works

Slots

A slot is one credential on one device. The front door lock is one slot. The garage keypad is another. The Wi-Fi network is a slot. Each slot lives on a property and has:

  • A provider — manual entry, Igloohome (smart lock), or future integrations
  • A rotation policy — every reservation, every N days, on-demand only
  • An audience — who can see it (guest, cleaner, maintenance, all)

Slots are defined once per property in Property → Access Settings.

Packs

A pack is a snapshot of credentials for one trip. When a reservation is created, the worker builds a pack from the property's slots, filtered by the audience. The guest sees the guest pack. The cleaner sees the cleaner pack.

Each pack has a window — the time range when the codes are valid. For guests this defaults to check-in through check-out. For cleaners it defaults to the turnover window. You can override the window per reservation; see per-reservation window.

The code lifecycle

  1. Created at pack generation. Encrypted at rest using ACCESS_PACK_MASTER_KEY.
  2. Delivered when the guest opens their stay portal, or when the cleaner opens their pack page.
  3. Rotated when a checklist step with rotate_access_codes action fires (typically turnover).
  4. Revoked when a checklist step with revoke_access_codes fires, or when you click Revoke on the reservation.
  5. Redacted 30 days after check-out by the worker. The code is permanently destroyed; the audit row stays.

Limits and requirements

  • Plan: Access Packs v4 is included on Host and Portfolio. Comply tier hosts see read-only delivery; rotation and revoke require an upgrade.
  • Encryption key: ACCESS_PACK_MASTER_KEY must be set on the API and worker (staging and prod use distinct keys). No key, no pack creation. See troubleshooting.
  • Providers: Manual is always available. Igloohome integration is in beta; other smart-lock providers are on the roadmap.
  • Audiences: A slot can target one of guest, cleaner, maintenance, or all. A pack can include multiple slots; the same slot can appear in multiple packs if its audience is all.

FAQ

What is the difference between a slot and a pack?

A slot is the device — "front door lock." A pack is the bundle of codes a specific person sees on a specific trip. Slots are configured once per property; packs are generated automatically per reservation.

How often do codes rotate?

Codes rotate when a checklist step with the rotate action fires. Most hosts wire rotation into their turnover checklist, so codes change every time a cleaner completes a turnover. See checklist-driven rotation.

Can I revoke a code mid-stay?

Yes. From the Reservation Access page, click Revoke. The pack is invalidated immediately and the guest portal stops showing the codes. The audit row is kept for 30 days.

What happens to old codes after a guest checks out?

The pack stays viewable for 30 days for dispute and damage claims, then the worker redacts the code values. The pack record and audit trail are kept indefinitely; only the secret material is destroyed.

Why did v3 get replaced?

v3 stored codes as free text on the reservation, with no rotation, no audit, and no per-audience filtering. v4 is encrypted, audited, and lifecycle-aware. The schema rewrite was the largest non-billing change of Q2.