Overview
Terms used across the Access Packs v4 surface. If you're reading host docs, reservation worker logs, or the AI agent's responses and a term feels unfamiliar, it's probably here.
Terms
Slot
A per-device credential definition on a property. The front door lock is one slot. The Wi-Fi network is another. A slot lives once per property and includes a provider, an audience, and a rotation policy.
Pack
A snapshot of credentials for one trip and one audience. One reservation typically has three packs: a guest pack, a cleaner pack, and (if the property has maintenance slots) a maintenance pack. Each pack is filtered from the property's slots by audience.
Audience
Who can see a slot or pack. Valid values: guest, cleaner, maintenance, all. A slot tagged all shows up in every pack; a slot tagged cleaner only shows up in cleaner packs.
Provider
The source of a slot's code. Valid values: manual (host enters the value), igloohome (smart lock via OAuth), and future smart-lock integrations.
Rotation policy
How often a slot's code changes. Valid values: every reservation, every 7 days, every 30 days, on-demand only.
Rotation trigger
A specific event that fires rotation. The most common trigger is a checklist step of type rotate_access_codes completing. Manual rotation from the Reservation Access page is also a trigger.
Revoke trigger
A specific event that invalidates a pack. Two sources: a checklist step of type revoke_access_codes completing, or a host clicking Revoke on the Reservation Access page.
Access window
The time range when a pack's codes are valid. Defaults to check-in through check-out for guest packs and a 12-hour band around turnover for cleaner packs. Can be overridden per reservation.
Window override
A per-reservation delta on the default access window. Stored on the reservation, not the property. Cleared by resetting to default.
Delivery
The moment a pack is first opened by its audience. Tracked per slot. A pack with no delivery one day before check-in is a reliable signal the guest doesn't have the codes yet.
Redaction
The permanent destruction of code values 30 days after check-out. Run by a worker job. Audit history is kept; code values are gone for good.
encryption_key_id
A column on every encrypted value pointing at the master key that encrypted it. Reserved for future key-rotation. Today, every value uses the same master key.
ACCESS_PACK_MASTER_KEY
The 32-byte base64 secret that encrypts and decrypts every slot value. Set on the API and worker in Railway, distinct per environment, not escrowed. Lose both copies and the codes are unrecoverable.
Readiness
The pack-level state shown at the top of the Reservation Access page. One of: Ready, Rotation in flight, Revoked, Window closed.
FAQ
Is a slot the same as a code?
No. A slot is the definition — what device, what audience, what rotation policy. The code is the value the slot currently holds. Codes rotate; slots don't.
Why are guest pack and stay portal different terms?
The pack is the data model — what credentials, what window, what status. The stay portal is the UI surface where the guest sees the pack. The pack is what the API serves; the stay portal is what the guest reads.