> ## 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.

# Let users connect their own calendars

> Let each of your app's users link their personal Google Calendar—so your app can read and write events on their behalf, privately.

Sometimes you don't want *your* calendar—you want each of your app's users to connect *theirs*. A scheduling app where every user manages their own bookings, a tool that drops events onto a customer's personal calendar, a team app where each member syncs their own meetings.

Unlike [your organization's calendar](/connected-services/google-calendar/connecting), this mode needs **no setup in Settings**. There's nothing to connect or grant—the agent builds the whole flow into your app.

## How it works for your users

```mermaid theme={null}
flowchart LR
    U["👤 Your user"] -- "taps Connect" --> App["📱 Your app"]
    App -- "opens Google sign-in" --> G["🔐 Google consent"]
    G -- "approves" --> SD["☁️ Stardeck stores it"]
    SD -- "returns to app" --> App
```

<Steps>
  <Step title="The user taps “Connect Google Calendar”">
    A button you ask the agent to add. It sends the user to Google to sign in.
  </Step>

  <Step title="They approve access">
    The user grants calendar access to their own Google account.
  </Step>

  <Step title="They land back in your app">
    Google returns them to your app, now connected. From then on your app can work with that user's calendar.
  </Step>
</Steps>

Each user's calendar is private to them. One user connecting their calendar never exposes it to another user, and you—the app owner—don't see their personal events.

## Build it

Open the app's project chat and describe the experience:

```
Add a "Connect Google Calendar" button to each user's settings page so they can link their own calendar
```

Then describe what to do with it:

```
Once a user has connected their calendar, let them see their upcoming events and book new ones from the app
```

The agent handles the connect button, the sign-in handoff, and reading or writing each user's events.

## Manage connections

Because these calendars belong to your users, they're managed inside your app—not in your dashboard. Ask the agent to build whatever your users need, for example:

```
Show whether the current user has connected their calendar, and give them a way to disconnect it
```

When a user disconnects, Stardeck revokes the access with Google and removes their stored connection.

## Next steps

<CardGroup cols={2}>
  <Card title="Your org's calendar" icon="building" href="/connected-services/google-calendar/connecting">
    Connect a single shared business calendar instead
  </Card>

  <Card title="User Authentication" icon="user-lock" href="/user-authentication">
    How your app identifies the users connecting their calendars
  </Card>
</CardGroup>