> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure booking settings

> Set party-size limits, booking durations, standard duration, guest duration choice, and no-show timing.

Booking settings define the valid inputs used by staff and guest booking flows. Change them as a coherent set because the API validates the complete settings payload and later booking requests against it.

## Who can do this?

**Owners and Managers** may change booking settings.

## Where to do it

Use **Bookings** in the Management web app for list, calendar, and details. Configuration is under **Settings → Booking**; the operational seating/order handoff is in **Live Floor**. Mobile has corresponding booking, detail, settings, and floor views.

## Steps

1. Open **Settings → Booking** for the correct store.
2. Set minimum and maximum party size. Maximum must be at least minimum, and both must be positive.
3. Manage the available positive durations and select one of them as the standard duration. Do not remove the standard option without choosing another.
4. Choose whether guests may set their duration. In the current web implementation, guest staff selection is forced off and party-size selection remains available rather than exposed as configurable switches.
5. Set the positive no-show threshold in minutes, save changes, and wait until the unsaved state clears.

## Platform notes

Management web and mobile use the same booking and status endpoints. The guest web app can create bookings; guest bookings start Pending, while authenticated store staff manage operational bookings. Guest and table assignments are separate links.

## Market notes

The flow is the same in GB and Germany. Date, time, and calendar labels follow the store market and time zone. Use the displayed local time; a booking stores a local civil date and time.

This guide was verified on 17 July 2026. Saved status, API authorization, and server validation of time windows and table occupancy are authoritative.

## Troubleshooting

* Saving fails when durations are missing, duplicated/invalid, not ordered as required by the API, or when party-size bounds are reversed.
* Only Owner and Manager can update settings. Owner, Manager, and Staff can use booking operations, but operational access does not grant configuration access.

## Related articles

* [Create a booking](/en/bookings/create-booking)
* [Edit or reschedule a booking](/en/bookings/edit-or-reschedule-booking)