As you may know, your reservable resources can be set to be “non-adjacent” to the previous resource when they are not physically located next to each other in your venue/facility. When resources are set as non-adjacent, reservations with multiple resources assigned will not be allowed to schedule across the 2 resources that are set as non-adjacent. This ensures that groups are not separated (potentially on different sides or floors of your facility) when larger groups need multiple resources for their reservation.
For example, let's say that your facility has 8 reservable bays with 4 on the left side of the venue and 4 of them on the right side of the venue. You may have set up your resources with the non-adjacent setting so that a 2 bay reservation is not booked on bays 4 & 5 (which would otherwise put the group on bays that are not physically next to each other).
When considering reservations requiring 4 or fewer bays, this is a good thing and ensures the group will always be placed on adjacent bays. What this also means is that, unless this override toggle is selected, reservations requiring 5 or more bays will NEVER be able to make a reservation at your facility because they would ALWAYS need to be placed on non-adjacent bays (and in this example, the maximum number of consecutive bays is 4).
This toggle (Non-adjacent Resource Override) allows you to override the non-adjacent resource settings for certain situations like the one noted above (reservations needing 5 or more bays).
For facilities with non-adjacent resources, it is also common to create several different packages to account for these situations. For example, the admin in our example above would be smart to create a package for group sizes requiring 1- 4 bays and then a second package for group sizes requiring 5 - 8 bays.
Please don't hesitate to reach out to your RKd representative with help navigating these more complicated package set up situations and we would be more than happy to assist!
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article