IXL CORE
All guides
SchedulingGuide Β· v1.0

Publish a public booking page

Create a self-service booking page backed by staff availability and share its public link, subject to your plan's active-page limit.

A booking page is a public offering you publish so people outside the organisation can book time against your staff’s availability. Each page has an unguessable public link that acts as its address, and bookings made through it appear on the calendar as ordinary appointments.

Before you start

  • You need the scheduling.booking_pages.manage permission.
  • At least one provider must have their Availability set up β€” a page’s open slots come from each provider’s availability editor.
  • The number of active booking pages is capped by your plan’s external-booking entitlement; the panel shows your usage and warns when you reach the limit.

Steps

  1. Open Scheduling β†’ Booking pages.

    [screenshot: Booking pages panel with the active-page usage]

  2. Start a new page and enter a Title and a Duration (min) (defaults to 30).

  3. Under Providers, search staff and add one or more people whose availability will back the page; each appears as a chip you can remove. At least one provider is required.

  4. Select Create booking page. New pages are created active, so this consumes one of your entitlement slots β€” if you are at the limit, deactivate another page first.

    [screenshot: Create booking page form]

  5. On the saved page, copy the Public link with Copy and share it. Use Activate / Deactivate to control whether the page accepts bookings, and View bookings to see appointments made through it.

Result

The page is published with a public link. External visitors open it with no login β€” the slug in the link is the credential β€” view the offering, fetch free slots (clamped by the page’s booking horizon and minimum notice), and book by giving their name, email and a chosen slot, which creates an appointment on your calendar. If the slot was taken in the meantime the booking is refused so two people cannot claim the same time. Deleting a page deactivates it and detaches its providers. A slug from one organisation can never reach another.

Put this into practice