> 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/members/managing-member-availability.md).

# Member availability

Workspace admins can review and update another member’s timezone, weekly hours, and vacation coverage.

Open **Settings → Members**, find the person, and choose **Manage User Preferences** from their action menu.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2Fwnk2XtIWUmpkxtZIFk0m%2FCleanShot%202026-09-10%20at%2021.27.28%402x.png?alt=media&amp;token=50e784d1-e199-4726-a526-1b9a7f60294c" alt=""><figcaption></figcaption></figure>

## Timezone and weekly hours

Choose the member’s **Timezone**, then click **Save timezone**. This is the timezone used for their weekly hours.

Under **Weekly availability**, turn on the days they accept meetings and set the start and end times. Use **Add new time slot** for a break within a day, or **Copy time slots to other days** to reuse a schedule. Click **Save** in the weekly availability card when finished.

The timezone and weekly hours have separate save buttons. Saving one section does not save edits in the other.

Use **Preview availability** to open the calendar troubleshooter. The event type, calendar conflicts, and booking rules can narrow the hours guests can actually book. See [Unavailable times](/settings/find-unavailable-times.md).

## Vacation coverage

Under **Vacation coverage**, choose a **Covering colleague** and click **Save coverage**. That colleague receives meetings when vacation coverage is enabled for the workspace.

**Detected vacations** shows time away detected for the next three months. Choosing a covering colleague does not create a vacation or turn on the workspace’s vacation routing.


---

# 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/workspace-settings/members/managing-member-availability.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 `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.