> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/working-hours.md).

# Working hours and named sets

Open **Settings → My Availability** to choose the weekly hours guests can book with you.

## Set your main hours

Choose your timezone, days and time ranges. Add a separate range for a midday break. Review before/after buffers and minimum notice, then save.

Working hours define when you are open for bookings. Busy events on a checked calendar and out-of-office blocks can still remove times inside those hours. See [Calendars and availability](/scheduling/availability.md).

## Create a named set

Use **Working-hour sets** for event-specific hours, such as “Partner calls” or “Evenings.”

1. Enter a **New set name** and select **Add set**.
2. Open the set and edit its weekly ranges.
3. Save the ranges.
4. Configure the event to use the set by name.

An event using a named set uses that member's hours of the same name. If the member has no matching set, it falls back to their main hours. Removing a set also makes affected events fall back to main hours.

## Check the booking result

Preview the event in a date range that contains your expected hours. Check the guest timezone, calendar conflicts, event hours and booking horizon if a time is missing.

**Hold buffers on my calendar** adds private busy Buffer events around new meetings on your primary calendar. Save that option separately and verify it with a controlled booking.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/working-hours.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.