> 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/workspace-settings/vacation/mark-calendar.md).

# Mark your calendar

Use your primary connected Google Calendar for automatic vacation detection.

1. Create an event covering the days you are away.
2. Select **All day** and set your availability to **Busy**.
3. Save the event in Google Calendar.
4. In Distro, review **Detected vacations** in your member preferences and confirm the dates.

Distro checks long, uninterrupted busy periods over the next three months. Adjacent periods can be grouped, including Friday-to-Monday periods. Detection uses calendar busy time, so check the detected dates rather than relying only on an event’s title.

Automatic Outlook vacation detection is not supported. A normal partial-day busy event still blocks its calendar time, but does not configure vacation coverage.

Your admin must separately enable removal from distribution or ownership-rule coverage in [Vacation](/settings/workspace-settings/vacation.md). Choose a covering colleague in [Profile](/settings/personal-settings/profile.md), or ask an admin to update [Member availability](/settings/workspace-settings/members/managing-member-availability.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.distro.so/settings/workspace-settings/vacation/mark-calendar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.