Letting an Owner Block Their Own Dates Without Handing Over Your Calendar

The message arrives on a Sunday evening: “We’re thinking of coming down for the second half of August, can you keep it free?” It is the owner of Villa 1, it is their house, and they are entirely within their rights. It is also the third owner message this week, it came by text, and by the time you get to your laptop you are not sure whether they meant the 15th or the 16th.

Owner stays are part of the job when you manage property for someone else. The owner has a right to use the place. What they should not have is the ability to put a block on your live calendar, over a guest who booked a month ago, while you are asleep.

This guide covers the middle ground: how an owner can ask for their dates themselves, and how you keep the final say.

The two bad options

Most managers end up choosing between two ways of handling owner stays, and both cost something.

Option one: you are the switchboard. Owners text, email or call, and you block the dates by hand. It works until it doesn’t: a message gets buried, the dates are ambiguous, or you block the property in one system and forget another. Nobody has a record of who asked for what, or when.

Option two: you give the owner a login. In most booking tools that login is the same kind of access your staff get. Now the owner can see your other properties, your revenue across the portfolio, and your pricing, and they can block dates straight onto a calendar that feeds your channels. We wrote about the same problem from the staff side in Why Your Cleaning Team Can See Your Revenue: access built for one kind of person always ends up given to another.

The owner’s need is narrow. They want to see how their property is doing, and they want to reserve some dates. They do not need to edit anything.

A third option: the owner asks, you decide

In Airflow, an owner never writes to your calendar. They make a request. You approve it, propose different dates, or decline. Only an approval creates a block.

That means the owner gets a self-service way to ask for dates, with a record of every request, and you keep the decision about what goes on a calendar your guests and channels depend on.

Step 1: Invite the owner to their property, and only that property

Open the property’s settings and go to the Owner Access tab. Under Property Owner Dashboard, enter the owner’s email in Invite a property owner and click Invite.

The owner gets an invitation email and signs in from the link. There is no password to set. What they see is a stripped-down portal scoped to that one property: its bookings, its calendar and its revenue. They do not see your other properties, your team, your billing, your connected payment and accounting services, or your organisation settings.

That scoping is enforced on the server, not just by hiding buttons. We ran a dedicated security audit of what an invited owner can reach, closed every hole it found, and re-tested each one live. An owner who tries to edit the listing, change prices or touch a booking is refused by the system, not just kept away from the button.

From the same tab you can see who you have invited, whether they have accepted, and Revoke their access at any time.

Step 2: The owner requests their dates

When the owner signs in, the first thing they see on their dashboard is a Block dates card. It says what it does: they request dates, and their property manager confirms before anything goes on the calendar.

They fill in:

From and To, the dates they want.
Reason, a short note such as “Owner use” or “Family visiting”.
Repeat, which is either One-off or Every year for a set number of years (between 2 and 10), for owners who take the same fortnight every summer.

Then they click Request. Airflow will not accept dates in the past, and it will not accept a second pending request for the same dates.

Below the form, the owner sees every request they have made and its status. They can Withdraw a request that is still pending, so a change of plan never needs a phone call.

Step 3: You approve, propose dates, or decline

The moment a request is made, everyone on your team with an owner or manager role gets an email. The request also appears on your portal dashboard under Owner block-date requests, marked Action needed, and on that property’s Block Dates tab.

You have three choices:

Approve. Airflow checks the dates against the property’s bookings and existing blocks at that moment, not when the owner asked, and then creates the block. The owner is emailed to confirm.
Propose dates. If the owner’s dates clash with a booking, offer alternatives instead of a flat no. Enter new From and To dates, add an optional note, and send it. The owner sees Accept new dates or Decline on their dashboard, and nothing is blocked until they accept.
Decline. Add an optional reason. The owner is emailed.

Yearly requests: each year is checked separately

When you approve a yearly request, Airflow checks every year on its own. If a guest has already booked the second of three years, the other two are blocked and the clashing year is skipped. The owner’s confirmation email says which years were blocked and which were not, so nobody finds out in July.

What an approval actually does

An approved request becomes a real availability block on the property, recorded as coming from the owner, with the owner’s note attached. It is the same kind of block you would add yourself, so:

The dates close on your own booking page. A guest cannot book them.
The block is included in the calendar feed Airflow publishes for the property. Any channel you have connected to that feed picks it up on its next sync. If channel syncing has ever let you down, Why Your iCal Sync Keeps Breaking explains why the timing varies.
You can undo it. If the owner’s plans change after approval, remove the block from the property’s Block Dates tab like any other.

Every request and every decision is logged, so when an owner asks in November why August was not blocked, you can show them.

Honest limits

A pending request does not hold the dates. Until you approve it, the dates stay open, and a guest can book them in the meantime. That is deliberate, because an unanswered request should never stop a paying guest, but it means you should answer requests promptly. If a booking lands first, approval will not block over it. Propose other dates instead.
Owners cannot block dates directly. That is the design, not a gap. If you want an owner to have direct control of the calendar, this is not that feature.
Every invited owner gets the same read-only view. There are no per-owner permission switches in the portal yet.
Channels update on their own schedule. Airflow publishes the block right away, but each channel decides when to read the feed.

Next step

Pick one owner who regularly asks for their own dates and invite them to their property from the Owner Access tab. The next time they want August, they will ask in the portal instead of by text, and you will approve it in one click. For how owners see their money as well as their dates, read Owner Statements That Write Themselves, and for the full picture of how Airflow runs a portfolio, see how it works. Ready to set it up? Get started with Airflow.