The Calendar
One shared calendar for the whole ownership group, with the rules your group already agreed to, enforced without anyone having to police them.
Everyone can see the same calendar. Nobody has to be the one who keeps it.The group text where somebody says “are you up the weekend of the 12th?” and three people answer and one doesn't, and then two families arrive on the same Friday.
One calendar the whole ownership group can see.
Shared booking calendar
Every owner books their own stays. Everyone sees the same picture, at the same time, without anyone forwarding a screenshot of a spreadsheet. The calendar is the property's single source of truth about who is where and when.
Owners book directly: no request-and-approve queue, no gatekeeper. Each booking carries who booked it, the dates, and the type of stay. Bookings show in the owner's own identity colour, so a month reads at a glance: you learn the shape of the summer without reading a single name. The current month shows in full, with a compact look-ahead beside it so you can see next month's density before you commit to a date. There is no “admin” who owns the calendar, because in a family that role is a burden rather than a privilege.
When two owners want the same weekend, the software tells you. It doesn't decide.
Conflicts flagged, never auto-blocked
Most booking systems award a contested date to whoever clicked first. That's the right answer for a hotel and the wrong one for a family. Casa Cabana surfaces the overlap, names who's involved, and leaves the conversation to the people who have to live with it.
Overlapping bookings are detected automatically the moment they're created and shown as a conflict on both stays and on the calendar. Neither booking is deleted, hidden, or silently demoted. The people involved get the information and the room to sort it out: a phone call, a trade, a split week. The product's opinion is that software should make a disagreement visible and early, not resolve it by a rule nobody agreed to. This is the most deliberate design decision in the product.
The agreement your group already made, enforced without anyone policing it.
Booking rules and season quotas
Most groups have rules: two peak weeks each, no more than three consecutive, first weekend of July rotates. Those rules usually live in someone's memory and get enforced by whoever is willing to have the awkward conversation. Put them in the calendar and they enforce themselves.
Set limits per season and per owner. The rules apply as bookings are made, so nobody has to audit the calendar after the fact or raise it at the next family dinner. Because the rules are visible to everyone, they stop being one person's interpretation and become the group's shared agreement. Change them when the group changes them.
Ask for the place to yourself, and let the group answer.
Private-stay requests
Sometimes you need the property to yourself: a milestone birthday, a work retreat, a week with your in-laws. Request it, and the other owners vote. The answer is recorded, so nobody relitigates it in August.
A private-stay request marks a booking as exclusive and asks the other owners to approve. Votes are recorded against the request and the outcome is visible on the booking itself. It exists because “can we have it to ourselves that week?” is a question every shared property faces, and handling it by group text produces a decision nobody can find three months later.
Spouses, kids and guests are part of the group. They don't need accounts.
Household members
A cabin weekend is rarely one person. Add the people coming with you so the group knows who's actually going to be there and how many beds are spoken for, without creating a login for a nine-year-old.
Household members attach to an owner and appear on bookings. They never count as owners, never consume a seat, and never need to be invited or managed. The product charges per property rather than per person, so there is no incentive to under-report who's coming, which means the calendar stays honest about capacity.
Nights used, per owner, with nobody keeping score in their head.
Fairness view
In every shared property there's a quiet running tally of who uses the place more. Making it visible defuses it. Making it invisible lets it grow.
A summary of usage by owner over time: nights booked, how they distribute across the year and across seasons. It doesn't judge and it doesn't enforce; it just removes the ambiguity that lets resentment accumulate. Most groups find the numbers are closer than anyone assumed, and the ones where they aren't now have a fact to discuss instead of an impression.