The old Access tab tried to be everything at once. Whether your guest was opening their stay twelve hours before check-in or halfway through the trip, they got the same wall of ten or thirteen blocks: codes, parking, Wi-Fi, house rules, check-out, all stacked together. That works on a desktop with infinite scroll. It doesn't work on a phone at midnight when someone needs the keypad code right now.

We've rebuilt the default tab. It's now called My Stay, and it composes itself based on the current phase of the stay.

What's different

Pre-arrival, a guest sees five things: a greeting, navigation buttons (Google Maps · Waze · Apple Maps), their dates, directions to the property, and how to reach the host. That's it.

Check-in day, the same stay shows codes, Wi-Fi, smart-home access, and entry instructions — the things you need in the moment of arrival.

Mid-trip, codes and Wi-Fi stay visible. Directions disappear. House rules and amenities surface. The card list contracts to what's useful during the stay itself.

Checkout day, house rules step back and trash and check-out procedures step forward. After checkout, almost everything fades — what remains is a thank-you and a prompt to leave a review.

Where the content comes from

The redesign isn't just visual. It also fixes a problem we've been carrying for a year: every property had two copies of parking, house rules, and check-out instructions — one on the access pack and one on the property guide. Updating one didn't update the other.

That ends here. The three duplicated columns are gone from access packs. The property guide is now the single source of truth for narrative content. Access packs hold the things that are per-reservation: codes, Wi-Fi credentials, entry steps.

We migrated the existing data automatically. If a property had varied content across reservations (different parking notes for different stays, for example), we kept the most common version as the property default and wrote per-stay overrides for everything else.

Per-stay overrides

Most stays use the property defaults. But sometimes one reservation needs something different — a guest with a boat trailer who needs the alternate parking spot, or a wedding party where you want to relax quiet hours.

On the reservation's Access tab in your host UI, you'll now find a Per-stay guide overrides panel. Pick a section, write a one-off version, save. The guest sees the override; everyone else still sees the property default. Clear the override and you're back to the default in one click.

What you need to do

Nothing. The migration runs automatically on the next deploy. Existing properties keep their access codes and Wi-Fi exactly where they were. The three migrated columns now live in your property guide — same content, same wording, just one home for it.

The Access tab on your guest's stay page now reads "My Stay." The path is the same, so any links you've shared continue to work.

If you want to see what guests see at each phase, you can preview a stay through the shareable invite link — open it in an incognito window and the view reflects the current phase.

Roadmap

A few things we didn't ship in this pass:

  • Pinning cards across phases for hosts who want full control.
  • A Guide tab cleanup — that tab is still its full 40+-section encyclopedia. We'll trim it in a future pass.
  • Bulk overrides across multiple reservations. For now, overrides are per-stay; if the same change applies broadly, edit the property guide.

If any of these are blockers for you, let us know.

Read the host doc: The My Stay tab · Per-stay overrides.