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

# Calendar Settings

Connect your Google Calendar or Outlook Calendar to sync meetings into Zero. Synced events are automatically linked to matching contacts, companies, and deals, and can optionally create new contacts from your meeting attendees.

## Connecting a calendar

Each person connects their own, in **Settings → Connections → Email & Calendar**: **Connect account**, then **Connect Google account** or **Connect Outlook account**, then through the provider's OAuth flow with every permission box left checked.

One connection covers mail and calendar together. See [Email & Calendar](/settings/mailbox-settings.md) for the email half.

## The calendar card

Each account's calendar card carries two pills: **Sync status** (**Syncing**, **Synced \<time> ago**, **Never synced** or **Error**, with a re-authentication warning and a **Reconnect** button if authorization lapsed) and **Event visibility**, showing the current default for new events.

## Event visibility

**Event visibility** sets the default for new events: **Public** to the workspace (where new calendars start) or **Private** to you.

Changing it only affects what syncs from then on, and Zero asks **"Apply visibility change?"** — **Only new activity**, or **Apply to all past activity** to rewrite existing meetings from this calendar too.

## Auto-contact creation

**Add everyone** creates a contact for each attendee with a valid email address; **Disabled**, the default, leaves it to you.

With it on, Zero still skips your own calendar address, attendees who are already contacts, and anyone on one of your workspace's own domains — teammates are never created as contacts.

Either way, synced events always link to attendees who already exist as contacts, along with their companies and deals.

## Sync behavior

Syncing is continuous, and edits in your calendar show up in Zero shortly after. The window is 12 months back to 12 months ahead.

To force a sync, open the **...** menu on the calendar card and choose a **Force sync** range:

* **Last 24 hours**
* **Last 7 days**
* **Last 30 days**
* **Lifetime** — the full supported window

Any manual sync also refreshes upcoming events.

## Managing a connected calendar

The same **...** menu offers **Rename**, **Re-authorize calendar** (the same flow as the **Reconnect** button when the status pill asks for it), and **Disconnect calendar**, which removes the calendar and the events that belong only to it. Meetings you shared with teammates who still have active calendars stay in Zero.


---

# 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.zero.inc/settings/mailbox-settings/calendar-settings.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.