What to keep out of your guide
A published guide is a public web page. This is what does not belong in one, and what to do with it instead.
Updated
A published guide has no guest login. Anyone with the link can open it, including guests from stays that ended months ago.
Treat it as a public page
The link is not secret. Guests forward it, save it, screenshot it and sometimes post it. Publish on the basis that anyone might read it.
Do not publish
- Permanent door or alarm codes. A code in a guide is a code known to every guest you have ever hosted.
- Passwords for anything other than guest Wi-Fi, particularly anything reaching your own devices or business systems.
- Personal documents — identification, insurance papers, ownership records.
- Financial details, including bank details for damage deposits.
- Anything revealing when the property is empty, such as a cleaning schedule.
- Information about children, including names and school details.
Better ways to share access information
Send temporary or guest-specific codes through your booking platform's messaging, close to check-in. If your lock supports it, use a code unique to each stay.
That way the information reaches the right guest at the right time, and expires with their booking.
Wi-Fi is a reasonable exception
Wi-Fi details are meant to be shared with guests, and putting them in the guide with one-tap copying saves real friction.
Use a separate guest network where your router supports it, so the password does not also reach your own devices.
If something has been published by mistake
Remove it from the guide, then change whatever it protected. Change the door code, change the password. Treat anything published as seen, because you cannot know who has already read it.
