> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daoco.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Calendar

> Connect one Google user's Calendar data through Google's hosted integration endpoint.

Google Calendar is a **Dev Testing** integration. Use it when one signed-in Google user should grant daoco access to calendar lists, free/busy data, and read-only event data during provider approval or testing. Google hosts the [MCP](/connections/integrations#what-is-mcp) endpoint for this connection.

## Connect Google Calendar

<Steps>
  <Step title="Enable Dev Testing">
    A workspace owner or admin must enable **Dev Testing** integrations in **Settings** -> **Preview features**.
  </Step>

  <Step title="Open the Google Calendar card">
    Open **Connections** -> **Integrations** -> **Dev Testing** and choose **Google Calendar**.
  </Step>

  <Step title="Approve Google OAuth">
    Choose **Connect**, sign in with the Google account whose calendars daoco may inspect, and approve the Calendar scopes.
  </Step>

  <Step title="Verify safely">
    Confirm the row is healthy, then run a minimal read-only [`/integration`](/connections/integrations#what-is-mcp) proof such as listing calendars. Do not list event details, calendar IDs, attendees, or times as a proof step.
  </Step>
</Steps>

## Workspace restrictions

If the Google account belongs to a restricted Workspace, ask the admin to trust the daoco OAuth app or allow these scopes:

```text theme={null}
https://www.googleapis.com/auth/calendar.calendarlist.readonly
https://www.googleapis.com/auth/calendar.events.freebusy
https://www.googleapis.com/auth/calendar.events.readonly
```

<Warning>
  This guide remains available for testing, but Google Calendar is not part of the normal Mail & Calendar production category.
</Warning>