> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/calendars-and-availability.md).

# Calendars and availability

How dCal knows when you are free: connect your Google or Outlook calendar, set your weekly hours in schedules, choose time zones, and understand how dCal turns all of that into the open times your gue

Your booking links only offer times when you are really free. dCal works that out from two things you set up once: the **hours** you want to take meetings, and the **calendars** where the rest of your day lives.

***

## How it fits together

| Piece            | Where you set it                  | What it does                                                                                                                                                                                      |
| ---------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Calendars**    | **Calendars** in the left menu    | Connected Google or Outlook accounts. Busy times block new bookings, and confirmed bookings are written to the calendar you choose.                                                               |
| **Schedules**    | **Availability** in the left menu | Your weekly hours, split into several ranges a day if you like, plus date overrides. A personal event can follow your working hours, use a saved schedule or have custom weekly hours of its own. |
| **Time zones**   | **Settings** and each schedule    | Your own time zone, and the time zone each schedule's hours are in. Guests see times in their own time zone and can switch to another.                                                            |
| **Event timing** | Each event in **Events**          | Length, slot interval, buffers and minimum notice decide how times are cut out of your hours, and the booking window how far ahead guests can book.                                               |

Out of the box you already have a **Working hours** schedule, Monday to Friday from 09:00 to 17:00. Connecting a calendar is the step that makes your links safe to share: until then, dCal cannot see meetings you booked elsewhere.

***

## In this section

| Page                                                                                                          | What you will learn                                                                                                                                                                         |
| ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md)          | Connect Google or Outlook, choose which calendars block times and which one receives bookings, test, reconnect or disconnect, and add an online meeting link.                               |
| [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md)                     | Create schedules, add several ranges a day and date overrides, choose the schedule each event uses, and set custom weekly hours for one personal event.                                     |
| [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md)                             | Your time zone, each schedule's time zone, the guest's own time zone and the picker they use, and daylight saving time.                                                                     |
| [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md) | Why a time is or is not offered: busy times, pending requests, buffers, minimum notice, how far ahead guests can book, the 10-minute hold, and what happens when a calendar cannot be read. |

## Related

* [Quickstart: your first booking link in 5 minutes](https://docs.dapta.ai/dcal/getting-started/quickstart.md)
* [Events (booking links)](https://docs.dapta.ai/dcal/events.md)
* [Share and embed](https://docs.dapta.ai/dcal/share.md)
* [Troubleshooting](https://docs.dapta.ai/dcal/troubleshooting.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://docs.dapta.ai/dcal/calendars-and-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.
