> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/settings/personal-settings/my-availability.md).
# Availability
Open **Settings → My Availability** in the Distro app. Turn on the days you accept meetings and choose the start and end of each working period.
Use **Add new time slot** to split a day around a break. For example, set 9:00–12:00 and 13:00–17:00 to keep lunch free. Use **Copy time slots to other days** when several days share the same hours.
Click **Save** when you're finished. **Preview availability** opens an [availability preview](/settings/calendar-troubleshooter.md) for a selected user or team schedule. Check the actual booking link for the full booking experience.
## Update hours from Chrome
Open Distro's side panel and choose **Availability**. Edit the days and time periods, then click **Save**. These are the same personal hours used by the main app. Leaving the tab before saving discards your edits.
## Hours and available times are different
Your weekly hours define when you are open to meetings. Calendar conflicts, meeting length, buffers, minimum notice, and the event type's availability strategy can narrow those hours further.
Check the timezone shown above your schedule. To change your account timezone, use **Settings → Profile** in Distro. The extension's **Meeting timezone** preference changes how meetings are displayed; it doesn't change your weekly schedule.
If a time is missing, follow [Find out why a time is unavailable](/settings/find-unavailable-times.md).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.distro.so/settings/personal-settings/my-availability.md?ask=&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 `automate deployments from our CI pipeline` 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.
