> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/system-restrictions/general-restrictions/reservation-and-event-restrictions.md).
# Reservation and Event Restrictions
During onboarding and system configuration, your PodPlay CSM will propose restrictions to guide your Customers toward desired behaviors. These system restrictions are adjustable after onboarding, too.
The following restrictions can be used on booking Reservations or Events:
Booking Horizon
The horizon is a window of days into the future when a Customer can book.
Max. Future Private Reservations per Customer
This value is 0 by default, meaning there is no limit for maximum future Reservations per Customers. If a value of 3 is added here, a Customer can only book 3 Reservations at a time. They need to attend the 1st Reservation before book a 4th Reservation (which would be the new 3rd future booked Reservation).
Max. Future Free Off-peak Hours
If a perk is provided to Members where the Off-peak hours are $0, the restriction will stop a Member from hoarding the free Off-peak slots. By default, the value is 0.
Max. Hours per Reservation
This restriction is default 0. If a value is entered here, this number correlates to the maximum hours bookable per Reservation. If the number 2 is entered here, then a Customer can book a Reservation up to 2 hours. Meaning, a Customer could book a 2 hour Reservation, then go back and book another 2 hour Reservation.
Require Card on Free Events/Bookings
By default, this toggle is turned off. If enabled, Customers will be required to have a credit card on file when signing up for a free Event or joining a Reservation that is paid for by the Reservation Holder.
Day Pass Strategy
The **Day Pass** is a Non-member fee paid when joining a Reservation. This feature is turned on to mitigate the free-rider problem, which is when a Non-member joins a Member’s Reservation, where the Member had a discounted cost for their booking. By turning this on, the Non-member would pay a fee to join the Member’s Reservation.
Max. Daily Reservations Using Play Passes
A Play Pass can be used to zero out the cost of a Reservation. By default the value here is null. If a value is entered, like 1, then a Customer can use a **Resv Play Pass** to book a Reservation for free one time per day, and if the same Customer wants to book a 2nd Reservation, they would need to pay for it with their credit card on file.
Event Signup Cancellation Penalty
By default this toggle is turned off. If enabled, when a Customer cancels their participation in an Event within a cancellation window, the Customer will be charged the full signup price (Non-member rate) regardless of any Membership tier. This means that if a Members-only Event does not have a Non-member Admission Rate higher than 0, and the Member’s Admission Rate is $0, there will not be a cancellation penalty.
Max. Future Event Signups by Type
By default the value here is null, meaning Customers can sign up for as many Events as they’d prefer. If a value is set here, it will limit the maximum amount of future Event signups allowed per Customer. Meaning, a value of 5 Open Play signups and 2 Clinic signups can be used to limit the Customer from joining more than 5 future Open Plays or 2 future Clinics. The Customer must attend one of these Event types before they can book another Event of the same type. This restriction can apply to any Event type or Custom Event type.
Max. Daily Event Signups using Play Passes
A Play Pass can be used to zero out the cost of an Event. By default the value here is null. If a value is entered, like 1, then a Customer can use a [**Play Pass**](https://help.podplay.app/en/categories/302593) to join an Event, like an Open Play, one time per day. If they want to join a 2nd Open Play, the Customer would need to pay. This restriction applies to both Non-members and Members alike.
Disable Concurrent Booking
Disable Concurrent Booking is a Feature Flag that stops a Customer from holding two overlapping bookings at once. When it is on, the App blocks a Customer from booking a Reservation or signing up for an Event if they already have another Reservation or Event that overlaps the same time. The point is to prevent a single Customer from tying up two slots at the same time, which costs the Club inventory and creates no-shows.
The flag is Default Off, so nothing changes for a Club until it is turned on.
{% hint style="info" %}
This is a Customer-facing restriction only. Admins are not bound by it and can still create overlapping bookings on a Customer's behalf.
{% endhint %}
**Conflict Scenarios Covered**
The validation looks at every kind of overlapping booking a Customer can have, whether they are booking a Reservation or signing up for an Event. The table below shows what the Customer already has in each row and whether the flag blocks the new booking.
| Customer already has | Booking a new Reservation | Signing up for a new Event |
| ------------------------------------ | ------------------------------- | -------------------------- |
| A Reservation they hold | Blocked | Blocked |
| An invitation to a Reservation | Handled at invitation, not here | Blocked |
| A Reservation they are an invitee on | Blocked | Blocked |
| An Event sign-up | Blocked | Blocked |
{% hint style="danger" %}
**Restrictions Not Available**
* There is no system limit to stop a Customer from booking during a certain time of day.
* There is no system limit to stop a Customer from only booking on certain days of the week.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.podplay.app/system-restrictions/general-restrictions/reservation-and-event-restrictions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.