TapStay property setup and how the Guest Portal works

Every property you create gets one permanent guest link. You fill that property with the things guests always ask for. Reservations then decide when the sensitive parts of it are visible.

• Create a property — TapStay generates a permanent link, QR code and NFC target for it.
• Fill in Wi-Fi, contact, house rules, arrival and access, checkout, photos and local picks.
• Publish it so the link opens for anyone who taps or scans.
• Add a reservation for each guest — this is what unlocks stay-sensitive details at the right time.
• Guests open the same link and get a portal that changes with their stay.

Start from the dashboard and add a property. Give it a name and address, pick the property type, and TapStay creates its permanent guest address —/stay/your-code. Each property gets its own card with status, key numbers and quick actions.

These are the guest essentials — the details that generate almost every message you get today. The setup flow saves as you go, so you can leave and come back.

You can also add, in the same flow:

• Check-in and check-out times, and the property timezone — TapStay uses the property clock, never the guest's device clock.
• Arrival and access details: building entry, floor, unit, key box or code, parking notes.
• Guest answers (FAQs) — the questions you keep answering by message.
• Local recommendations: coffee, dinner, groceries, pharmacy, things to do.
• A welcome message and a farewell message.

Photos and an optional welcome video set the tone before anyone arrives. Once the property is Active, these presentation assets stay visible in the limited public view even when no stay is running — unlike the operational details. While the property is still a Draft, the link is not open to the public at all.

A new property starts as a Draft. A draft link is not open to the public — only you, signed in, can preview it while you write.

Switch it to Active when you are ready. Active means the link, QR code and plaque work for anyone who opens them.

A reservation is simply the dates and times a guest is with you. Add one from the property card status strip, or from the Reservations card on Manage stay.

Reservations do three jobs:

• They tell TapStay when a guest should see stay-sensitive details.
• They drive the portal timeline: pre-arrival, check-in, in stay, checkout.
• They keep your dashboard honest about what is happening today.

The guest link is the same at every moment. What changes is how much of it is live.

• No reservation scheduled — the portal is intentionally limited: property identity, photos, welcome video, general check-in and check-out times.
• Reservation booked, arrival still far off — the portal frames the upcoming stay and getting-here context without exposing entry credentials.
• Shortly before check-in — a short pre-arrival window opens (currently 60 minutes before check-in on the property clock). It releases the exact address, arrival notes, floor and unit, and the access method, so an arriving guest can find the door. It deliberately does not release building entry codes, access codes or the detailed access instructions.
• From check-in onwards — check-in reads as available now and stay-sensitive details, including access codes, are shown.
• After the stay window closes — the portal steps back to its limited state and sensitive details are no longer exposed.

Your guest link is permanent and public. A neighbour, a delivery driver or a guest from six months ago can open it. So the server strips stay-sensitive fields from the public response unless a reservation makes the visitor eligible — the data never reaches the browser.

The exact address is treated as operational, not as public identity: outside a stay the public response carries no street address at all. It is released in the pre-arrival window — 60 minutes before check-in on the property clock, together with arrival notes, floor, unit and the access method — and throughout the active stay.

Access credentials get one extra layer. The pre-arrival window never carries building entry codes, access codes or detailed access instructions, and even inside a booked stay those remain hidden until check-in is reached on the property clock, then appear with the arrival details.

Preview on a published property opens the real public guest URL in a new tab. That is intentional: you see exactly what a guest would see at this moment, including the limited view when no stay is running.

The owner-only full view applies to drafts. While a property is not public yet, signing in lets you preview your own content so you can proofread it before you go live.

During an eligible stay the portal behaves like a calm, single-purpose app: the essentials on the home screen, details one tap away in sheets.

Local recommendations appear as Around You, with your own picks alongside useful nearby places.

Three ways in, one permanent address. Guest access lives on the Manage stay page for each property.

The Concierge answers guest questions from what you have saved and from what is available for that stay. It does not invent details, and it never reveals information that is currently private.

Guest Knowledge is where you turn the messages you keep answering into answers the Concierge can give for you. Every entry you add widens what it can handle.

Edits save immediately and the guest link serves them straight away — no republishing, no new QR code, no new plaque. Change the Wi-Fi password mid-stay and your current guest sees the new one the next time the portal loads.

• Property created, named and addressed correctly
• Property timezone, check-in and check-out times set
• Wi-Fi, host contact, house rules, arrival/access and checkout instructions saved
• Photos uploaded, cover chosen, welcome video added if you want one
• Guest answers and local recommendations filled in
• Property switched to Active
• Reservation added for the next guest
• Guest link previewed with a stay running
• Plaque, QR code or direct link in place and shared