Before you start
Confirm the reservation and physical lock mapping. Code reveal permission and live access approval are separate from viewing locks.
-
Open Bookings > Locks or the Locks page and match the reservation’s physical unit to the provider device. A correct device mapping is essential before interpreting any access state for the stay.
Confirm the mapped device Unit 402Door 402Physical unit 3BDoor 3B- Physical unit
- Accommodation assigned to the stay
- Device
- Mapped provider lock
- Physical unit
- Accommodation assigned to the stay
-
Use the separate authorized controls for revealing or changing a code. Keep any revealed value out of general chat, support reports and public house instructions.
Use protected code controls 402••••••Use protected code controls
- Code reveal
- Separate permission
- Sensitive values
- Dedicated protected controls
Creating a door code does not release it early or bypass guest access prerequisites.
- Sensitive values
- Dedicated protected controls
-
Check the guest access gate when reviewing door and Wi-Fi details in the guest app. General house rules must not become an alternative way to expose a value still behind a blocker.
Inspect guest access conditions 402••••••Inspect guest access conditions
- Guest access
- Release conditions for the stay
- House information
- Protected details remain gated
Creating a door code does not release it early or bypass guest access prerequisites.
- Guest access
- Release conditions for the stay
Check the result
The lock view shows the mapped device and recorded access state. The guest view reveals protected details only when its access conditions are met.
Limits and prerequisites
Creating a door code does not release it early or bypass guest access prerequisites.