Why an Access Request Can Be Declined

A Kaza visible in search, up-to-date availability, and yet an access request declined: the situation sometimes surprises members discovering how KazaKlub works. It deserves a clear explanation, because it's not a malfunction — it's a central feature of the system, not an oversight.

Being Findable Has Never Meant Being Bookable

On a classic booking platform, a displayed availability is almost a promise: if the date is free and payment is made, the stay is secured. KazaKlub works by a different rule: every access request, whatever the Kaza and whatever availability is shown, must be explicitly accepted by its owner. Nothing is automatic, at any stage.

This rule applies uniformly, even for very active Kazas or longtime members of a Klub: visibility and availability indicate that a request can be sent, never that it will be accepted.

Why a Decline Doesn't Need to Be Justified

An owner who declines a request doesn't have to give a reason, and this lack of obligation isn't a legal loophole: it's a necessary condition for the very principle of lending among close ones to work. A lent home remains, for the entire duration of the loan, a space its owner keeps a hand on — accepting a request means agreeing to open your home at a given moment, not giving up that right once and for all by publishing a listing.

The reasons for a decline, when they exist, are most often unrelated to the person making the request: a personal emergency, a change in availability between the calendar update and the request being received, or simply a preference for a different time. Reading a decline as a judgment on yourself is an understandable reaction, but rarely a well-founded one.

A decline says something about the owner's situation at that exact moment. It says nothing about the person who asked.

What This Changes for the Person Making the Request

This rule has a useful, often overlooked counterpart: it also protects the person sending a request. Access that's never automatic means no member can end up committed to a stay they hadn't actually wanted to host, with all the tension that can create afterward. Systematic approval guarantees that every accepted stay is genuinely accepted, not accepted by default.

In practice, a declined request can simply be redirected to another Kaza in the same Klub, or rephrased for different dates. Nothing about a declined request closes off future requests, whether to the same owner or to other members.

What This Changes for the Person Lending

For an owner, knowing that a decline requires no justification removes a common hesitation among newcomers: the fear of "having to" accept a request just because the Kaza is technically visible and available. That's never the case. Publishing a Kaza and setting its availability opens up the possibility of receiving requests; it commits you to accepting none of them.

Who This Explanation Matters To

It's for new owners, who sometimes worry about losing control by publishing their Kaza, just as much as for members who've just been declined and wonder if they did something wrong. In both cases, the answer is the same: the system is working exactly as intended, and it's precisely this systematic approval step that makes sharing possible without putting anyone in the position of having to accept what they don't want.