> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/scheduling/connect-your-calendar.md).

# Schedules and calendars

Connect Google Calendar or Microsoft 365, set your hours, share schedules, and find out why no times show.

A booking link offers the times inside its hours that are free on the host's calendars, once its booking limits are applied. The hours come from your **My availability**, a group's hours or a shared schedule.

{% embed url="<https://app.screendesk.io/recordings/70ba0cf8-100c-41cc-9384-77f50d61c63b>" %}

## Connect your calendar

Each host connects their own calendar, group members included.

1. Open **your avatar → Connected apps**.
2. Click **Connect** on **Google Calendar** or **Microsoft 365 Calendar**, sign in and approve access.
3. Under **Add new bookings to**, pick the calendar Screendesk adds each booking to. With Google, it must be a calendar the account owns.
4. Under **Check for conflicts**, turn on every calendar whose busy times should block bookings.

Changes save on their own. After adding calendars in Google or Outlook, use **Refresh calendars** in the connection's **⋯** menu.

{% hint style="warning" %}
A calendar marked **No access** blocks every booking while it's checked. Restore access and refresh, or turn it off. If the card says **Action required**, click **Reconnect**.
{% endhint %}

If your Microsoft 365 organization restricts app consent, ask your Microsoft 365 admin to approve Screendesk.

## My availability

Open **your avatar → My availability** to set the hours people can book you on the links you host. Turn on each day you take meetings and set its times. Add a second range for a break, or copy a day's times to other days.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FeLFNNOahTxrMcmchvubU%2Fdocs-panel-my-availability.png?alt=media" alt="My availability, weekly hours"><figcaption></figcaption></figure>

**Date overrides** replace the weekly hours for one date: add rows for split hours, or mark the date unavailable. Click **Save** when you're done.

The time zone is the one in **My profile**. Group links use the group's hours instead.

## Schedules

A schedule is a set of hours that several booking links share, like "Customer calls". Find them in **Bookings → Schedules**. Admins and editors create them with **New schedule**, each with its own time zone, weekly hours and date overrides.

Pick a schedule in a booking link's **Hours**. Editing a schedule changes every link that uses it.

## No times show

Check these in order:

1. The link is active, not paused or archived.
2. The hours: enabled days, time zone and date overrides.
3. The meeting fits inside the hours, with its buffers.
4. **Minimum notice** and **Booking horizon** leave times open.
5. The host's calendar is ready. The booking links list shows **Your calendar needs setup** if it isn't.
6. The host isn't busy on a checked calendar or another booking.

For a **Round robin** group, only the next member's free times show. **Maximize availability** offers every member's times.

Customers see times in their own time zone, which they can change on the booking page. A time can disappear while a customer books if someone else takes it first.


---

# 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.screendesk.io/scheduling/connect-your-calendar.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.
