Access Profiles

Access Profiles are reusable bundles of booking settings. Instead of configuring party sizes, deposits, policies, capacity and the rest inside every individual rule, you build a profile once and attach it wherever it’s needed. Change the profile, and everything using it updates.

You’ll find them under Settings → Policies → Access Profiles.

Why profiles

Rather than each access rule holding its own copy of every setting, a rule simply references a profile. This means:

You set your rules up once and reuse them across many slots.
Editing a profile updates every rule or ticket that points at it.
Your setup stays consistent - no drift between two slots that should behave the same.

Access rules pick a Table or Guest List profile; event ticket types pick a Ticket profile; events pick Event and Guest List profiles.

The four families

There are four families of profile, each suited to a different flow.

Guest List profiles

Used by guest-list access rules and events. A Guest List profile controls how name-on-the-list entries behave.

Field	What it sets
Venue access tier	The membership tier required - All, Exclusive (Premium) or Super Exclusive (Premium Plus).
Free / paid list	Whether joining the list is free or paid.
Surge	List surge pricing - a threshold and price applied as the list fills.
Party	Allowed party size for a guest-list entry.
Policy	The booking policy shown to guests.
Payment policy	A named payment policy enforcing a cancellation window on the list.
Window	The booking window (how far ahead and cutoff).
Capacity	The list’s capacity.
Checkout hold	Optionally hold the guest’s spot for up to 30 minutes while they complete checkout, auto-releasing if they don’t finish.
Admission rule	An admission rule group governing who qualifies and any perks.

See Guest list setup for a walkthrough of these guest-list fields.

Table profiles

Used by Table Reservation access rules. A Table profile controls how table bookings behave.

Field	What it sets
Party	Minimum and maximum covers.
Areas / tables	Which seating areas or tables the booking can use. If a shift covering the same hours closes an area, the rule only offers tables in areas open in both places.
Assignment	How the table is decided: assigned automatically, the guest picks a seating area or a seating area group (Sidedoor then seats them at a fitting table in it), or the guest picks the exact table from the floorplan.
Price list	Whether a deposit or minimum spend applies and the price list that sets the amount.
Deposit policy	Auto-cancels the reservation if a requested deposit goes unpaid within a named policy’s window.
Payment / policy	The payment policy and booking policy.
Confirmation policy	Asks the guest to reconfirm by a deadline, releasing the table if they don’t.
Duration	Booking length for this profile.
Optional add-ons	Add-on bundles guests can choose as extras (they can skip them). Drag a bundle’s handle to reorder the list - guests see them in that order.
Pre-orders	A mandatory pre-order, drawn from the same table bundles. Guests must choose at least one item before they can finish booking. Drag to reorder here too.
Waitlist	Offer a waitlist when the profile is fully booked, auto-seating guests as tables free up.
Late / No-show	Three thresholds: flag a booking late, auto-mark it a no-show and release the table, and when a held deposit is charged.
Checkout hold	Optionally hold the table for up to 30 minutes while the guest completes checkout, auto-releasing if they don’t finish.
Tags	Reservation tags applied to the booking.
Window	The booking window.
Max covers	Caps the total covers the rule takes across its whole service on a date; holds count until they expire. A shift covering the same hours can set its own max covers too - both need room.
Pacing	Caps the covers that may arrive in any 15-minute window on the rule. An empty window always takes one booking; once a window has an arrival, further bookings must fit under the pace. Works alongside Max covers - both need room. A shift covering the same hours can also cap pacing - a booking must fit both.
Max reservations per guest	Caps how many upcoming reservations one guest can hold on the rule. Only bookings on that rule count, and staff bookings made in the client portal aren’t limited.

When Assignment is set to Guest picks area, the list under it chooses what guests are offered - individual seating areas, seating area groups, or a mix. Leave the list empty to offer every group plus every area that isn’t in a group. Guests only see choices with a table free at their time, and when a deposit applies, the price shown for a group is the cheapest fitting table across all of its areas.

When a shift covering the rule’s hours sets its own Pacing, Max covers or Open areas, the profile editor marks the matching section Also limited by shifts and names the shift - with a warning if the shift’s limit is tighter than the profile’s own, since the shift caps first in that case. Shift and profile limits both apply: a booking must fit both.

A table rule backed by one of these profiles can also be published as a branded, guest-facing product, an experience. That switch lives on the access rule itself, not on the profile. See Experiences for the full walkthrough.

Event profiles

Used by events. An Event profile controls the booking behaviour attached to an event.

Field	What it sets
Payment / policy	The payment and booking policies.
Window	The booking window.
Bundles	Add-on bundles offered with the event. Drag a bundle’s handle to reorder the list - guests see them in that order.
Tags	Reservation tags applied.
Promo codes	Promo codes accepted for the event.
Visibility	Where and to whom the event is visible.

Ticket profiles

Used by an event’s individual ticket types. A Ticket profile controls per-ticket behaviour.

Field	What it sets
Window	The booking window for the ticket.
Tags	Reservation tags applied to ticket buyers.
Visibility	Where and to whom the ticket is visible.
Show capacity	Whether remaining capacity is shown to guests.
Checkout hold	Optionally hold the tickets for up to 30 minutes while the guest completes checkout, auto-releasing if they don’t finish.

The default profile

Each family has one built-in Default profile, shown as the first row in its list. It’s the fallback that applies whenever a booking doesn’t name a profile of its own:

When an access rule is set to “No profile - use venue defaults”, bookings through it use that family’s Default profile.
The Default profile applies as a whole. Picking an explicit profile replaces the default entirely - the two are never merged field by field.

The Default profile can’t be renamed or deleted, but every other setting on it is fully editable - so it’s the place to set your house-wide fallback behaviour (party sizes, deposit, policies and the rest). Tune it once and any rule left on “use venue defaults” follows it.

Working with profiles

Build the profiles you need in each family.
Attach Table and Guest List profiles to your access rules.
Attach Event and Ticket profiles when creating events and their ticket types.
Edit a profile any time - every rule and ticket referencing it picks up the change.