View Public Booking Settings

In this article

Before you start

• Sign in to the private Antylogic app with an organisation and location selected.
• Use the GB demo runtime for Harbor Demo Group and Harbor Soho when producing landing documentation captures.
• The user needs `reservation-automatic:use` to access the Public web tab.
• The user needs location viewing access to load the settings. `location:manage` is only required for changing toggles or saving warning text.
• Open `/:orgId/:locationId/location/optimization-configs?tab=public-booking` or navigate to reservation settings and select Public web.

Instructions

1. 1.

   Open Public web

   Open Harbor Soho's reservation settings and select Public web. The direct documentation link is `${APP_DEEPLINK_BASE}${ORG_ID}/${LOCATION_ID}/location/optimization-configs?tab=public-booking`, and the tab value must stay exactly `public-booking`.

2. 2.

   Confirm the settings load

   Wait for the settings cards to appear. If the app cannot identify the selected organisation or location, or if the user lacks viewing permission, it shows a state message instead of loading the location settings.

3. 3.

   Read publication status

   In Publication status, read whether the badge is Enabled or Disabled and check the Accept reservations from the website toggle state. For this guide, leave the toggle unchanged.

4. 4.

   Check table preferences

   Review whether table preferences are enabled. This tells the operator whether the public booking flow asks guests for no preference, an area, or a table type before they continue.

5. 5.

   Review the public URL and QR

   Read the Public URL field and identify the Reservation QR below it. The QR uses the same calculated public URL as the field.

6. 6.

   Review configurable warnings

   Scroll to Warnings during booking and review the warning list. A location can have multiple active or inactive warnings with a step, colour, trigger/rule, and optional blocking behaviour.

Validations and limits

• The Public web view opens only when the route parameter is exactly `tab=public-booking`; other values resolve to the Optimizer tab.
• If `reservation-automatic:use` is missing, the Public web tab is not shown and the screen returns to Optimizer.
• The location query runs only when organisation context, location context, and view permission are present.
• The settings are read through `GET /api/app/{orgId}/locations/{locationId}`.
• Only `public_booking_enabled === true` appears as Enabled; every other value appears as Disabled.
• Table preferences are enabled unless `public_booking_table_preferences_enabled` is explicitly `false`.
• The public URL and QR use the same calculated `publicUrl`; the URL is empty only when the organisation or location context is missing.
• Configurable warnings are read from `public_booking_warnings.items`; if only the legacy `public_booking_warnings.people` shape exists, the UI converts it into a People warning.
• Each warning shows whether it is active, whether it blocks the booking when triggered, and for Preference warnings whether it is shown on selected-name match or at the start of the Preferences step.
• The QR is displayed below the Public URL and uses the same calculated publicUrl.
• Do not copy the URL, download the QR, save warnings, or change toggles while documenting this view action.

Expected result

The operator has confirmed the public booking publication status, table preference setting, shareable URL, reservation QR, and configurable warning list without changing the location configuration.