Open a scheduling page from Scheduler → Scheduling pages and the editor shows six sections in a rail: Basics, Availability, Timing, Limits, Team, and Booking form. Availability is the second one, and its description reads “Add multiple blocks per day to model lunch breaks (e.g., 9-12 + 1-5).”

Four things sit in plain view because you have to decide them to share a working link: where the hours come from, the weekly grid itself, date-specific hours, and a one-line summary of the booking window. Everything else in the section — the booking-window controls themselves — lives behind the Advanced disclosure, which starts closed. A brand-new page you create with nothing but a title already has usable hours: Monday to Friday, 9:00 AM to 5:00 PM, with Saturday and Sunday off.

Each weekday has a switch and a list of time periods. Switch a day on and set a start and an end time. A day with no periods reads Unavailable. If every day is off, the editor says “This page currently offers no times.”

Below the weekly grid, Date-specific hours handles the exceptions: “Change your availability for specific dates, like holidays.” A date listed here replacesthe weekly rule for that day — it is not added on top of it.

The Repeat control at the top of the weekly grid has two settings: Repeat weekly (the default) and Does not repeat. Switch to Does not repeatand the seven weekday rows and the presets disappear — only Date-specific hours remains. Nothing is offered except the dates you add there. This is the right shape for a one-time class, an interview week, or a pop-up clinic.

Your weekly hours are not thrown away. The editor says so directly: “Your weekly hours are kept and will apply again if you switch back.”The slot preview also stops guessing on a one-off schedule — “Times are not previewed for a one-off schedule.”

The first control in the Availability section is a pair of choices under the question “Where do these hours come from?”:

A shared schedule is listed with its name, whether it is the default, and how many pages use it — for example Support hours · default · used by 3 scheduling pages. When a page is on a shared schedule, a band above the grid states the blast radius before you type: “Editing these hours changes Support hours, used by 3 scheduling pages.” If the usage count cannot be read, the band is honest about that instead of guessing.

If your organization has none yet, the section says “Your organization has no shared schedules yet.” and offers Create a shared schedule — give it a Schedule name and click Create. Existing schedules are managed from Settings > Scheduler under Availability schedules(“Reusable sets of hours that your booking pages can share.”), where you can rename, duplicate, Set as default, or remove one.

Open Advanced inside Availability and the question is “When can people book?” with three answers:

Whichever you pick, one plain sentence underneath states the result — for example “People can book through Mar 31.”, “People can book March 1 through March 31.”, “People can book up to a year ahead.”, or, once a fixed range has ended, “This page is closed to new bookings.” With the disclosure closed, the same fact rides the section summary as “Booking window: through Mar 31”.

When the weekly grid and a date-specific entry disagree about the same day, the answer is fixed and does not depend on the order you set them in:

Two more filters run after that, on the times these rules produced: the booking window drops dates outside it, and the scheduler removes any slot that is already busy — existing bookings, synced calendar events, CRM activities, and any required resource. See Scheduling Pages for how busy time is computed.

Turn on the Bookable windows layer on the Calendar and check a booking link in the Share a linksection, and that page's offerable time is drawn on the grid in the link's own color. Click a band to open a peek titled Bookable time, which names the link and offers Create here and Share link; with scheduler.edit it also offers Edit availability and Make unavailable.

In week and day views on a desktop-sized screen with a mouse or trackpad, you can drag across an empty stretch of a day column to open that time. Releasing opens a dialog titled Add availability with two choices, Offer this time and Make unavailable instead. Confirming writes a date-specific entry — exactly what the editor writes — and the calendar confirms with “Availability added for that date.” or “Marked unavailable for that date.”

If the range you drew belongs to a shared schedule, the dialog says so before you commit — for example “This changes Support hours, used by 3 scheduling pages.”— and offers to switch that page to its own hours first instead. If the shared schedule is one you may use but not change, the dialog explains that only this page can be changed.

• scheduler.view — required to open a scheduling page and read its hours.
• scheduler.edit — required to change hours, add or remove date-specific entries, change the booking window, or drag on the calendar. Without it the Availability section is read-only: the hours and the resolved booking-window sentence still render, but there are no inputs.
• scheduler.admin — required to change the organization-wide scheduler settings that sit alongside availability, including the workspace booking URL.
• A shared schedule can also be read-only for you specifically: “You can use this schedule but cannot change its hours.” You can still point a page at it and change that page's other settings.