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

# Connect your calendar

> Link your organization's Google account, grant it to your apps, and set a default—all from Settings → Integrations.

This guide covers connecting **your organization's own Google Calendar**—a single shared account your apps can read and write. If instead you want each of your app's users to connect their *personal* calendars, see [Let users connect their own calendars](/connected-services/google-calendar/end-user-calendars) (no setup here required).

## Connect a Google account

<Steps>
  <Step title="Open Integrations">
    In your organization dashboard, go to **[Settings →
    Integrations](https://www.stardeck.ai/dashboard/settings?tab=integrations)** and expand **Google
    Calendar**.
  </Step>

  <Step title="Click Connect">
    Click **Connect Google Calendar**. You'll be taken to Google to sign in and approve calendar
    access.
  </Step>

  <Step title="Approve access">
    Choose the Google account whose calendar you want to use and approve the permissions. Google
    sends you back to Stardeck, and the connection appears in the list.
  </Step>
</Steps>

You can connect more than one Google account—each shows up as its own connection with the account's email.

## Grant the connection to your apps

A connection does nothing until you allow an app to use it.

<Steps>
  <Step title="Open Grants">On the connection, click **Grants**.</Step>

  <Step title="Add an app">
    Pick an app from your organization and grant it access. Repeat for each app that should use this
    calendar.
  </Step>

  <Step title="Set a default">
    If an app can reach more than one Google account, mark one as the **default** (the star). The
    agent uses the default when you don't name a specific account.
  </Step>
</Steps>

<Note>
  An app can only use connections you've granted to it. Granting is also how you keep calendars
  separated—an app you didn't grant can't see or touch the connection.
</Note>

## Build features

Once a connection is granted, open the app's project chat and describe what you want:

```
Use my Google Calendar to book consultations—create an event with a Meet link when someone picks a slot
```

The agent builds against the granted connection automatically. See [What you can build](/connected-services/google-calendar/overview#what-you-can-build) for more examples.

## Re-authorize a connection

If a connection shows an **invalid** or **revoked** status, Google access has lapsed—usually because the account's permission was withdrawn in Google's own settings, or the password changed. Click **Re-authorize** on the connection and approve access again. Your grants and defaults are preserved.

## Disconnect

Click **Delete** on a connection to remove it. Stardeck revokes the access with Google and stops any app from using it immediately. Apps that relied on it will no longer be able to reach that calendar, so re-point them to another connection if needed.

## Next steps

<CardGroup cols={2}>
  <Card title="Users' own calendars" icon="users" href="/connected-services/google-calendar/end-user-calendars">
    Let your app's end users connect their personal calendars
  </Card>

  <Card title="What you can build" icon="sparkles" href="/connected-services/google-calendar/overview">
    Example calendar features to ask the agent for
  </Card>
</CardGroup>