Security & Reservation Information
How to Share Door Codes and Entry Details Safely
Direct answer
Share door and building codes only with a guest who has passed the required booking check, and only after the configured release time and within the valid stay window. Keep live codes out of public guides, photos, and reusable templates. When the lock permits it, expire or replace access after checkout, cancellation, or a security event.
Create a Free Guest Guide with stayV HostKey takeaways
- Remove live access codes from public guides, photos, and reusable messages.
- Check booking status, release time, and validity before disclosure.
- Expire or rotate access after checkout, cancellation, or a security incident.
Why should entry credentials be separate from general guidance?
A public link can move outside the booking through forwarding, screenshots, and browser history. An obscure URL or search directive does not verify the person opening it.
Use a placeholder such as [Door code] in general instructions and tell the guest where the protected value will become available.
What conditions belong in a safe disclosure check?
At minimum, verify that the reservation is active, belongs to the property, has reached the host's release time, and has not passed checkout. These conditions should be checked on the server rather than trusted from a browser flag.
- Active reservation and matching property
- Host-configured pre-arrival release time
- Expiry on checkout or cancellation
- Limits and audit records for repeated failed access
How should a code be managed before and after a stay?
Do not paste the credential into an article or draft before the stay. Prepare access for the intended dates, then confirm that a previous guest's access no longer works after departure. Recalculate release conditions after a cancellation or date change.
What is the fallback when a guest cannot enter?
Verify the booking and physical location before repeating a code across more channels. Check whether the guest is using the building code or unit code, then review lock power, timing, and the property's real backup entry process.
How to apply this in stayV Host
Do not place a live code in stayV L0 cards or the free message generator. Use placeholders and manage protected values only in the current booked-guest fields.
A Free guide password does not prove booking identity and must not be used as the release mechanism for an entry credential.
This article provides general operational guidance, not a security guarantee or legal advice for a particular lock or building.
Frequently asked questions
Can a noindex page safely contain a door code?
No. Noindex is a search signal, not access control. The server should return a live credential only after checking the booking, release time, and validity window.
Can every reservation use the same code?
If the device supports temporary codes, align them with each stay. If a fixed code is unavoidable, document who receives it, when it is rotated, and how an exposure is handled.
Does a building entrance code need the same protection?
A building code also grants physical access. Review the building's rules and risk, and do not place the value in a public map, photo, or reusable template.