# Connected accounts

> A person connects their own Gmail, Calendar, Drive, Notion, Slack or email account to your app, and the agent reads only that person's data.

## What a person connects

Each person approves their own account. Harny reads only that person's connected account. You do not read or store their password. The person approves a link, and that is the whole step for them.

The providers are:

- `gmail`
- `calendar`
- `drive`
- `notion`
- `slack`
- `email_bridge`

## Connect, sync, list, disconnect

Start a connection with `POST /v1/context-sources/{provider}/connect`. The response gives a link. The person opens it and approves access.

| Action | Route |
|---|---|
| Connect | `POST /v1/context-sources/{provider}/connect` |
| List | `GET /v1/context-sources` |
| Sync | `POST /v1/context-sources/{provider}/sync` |
| Get a reauth link | `GET /v1/context-sources/{provider}/reauth-url` |
| Disconnect | `DELETE /v1/context-sources/{provider}` |

In the SDK, call `client.connect_oauth(provider)`.

Call these routes from your server, with your app key in the `Authorization: Bearer` header and your id for the person in `X-Harny-User`. Do not call them from a browser.

Disconnecting ends Harny's access to that account.

## Google access for Gmail, Calendar and Drive

Gmail, Calendar and Drive connect once Harny has approved Google access for your app. Request that approval in the console. Until it is approved, those three providers do not connect.

## What the agent can read

The agent reads only the connected data of the person it is working for. Each app's data is separate, and each person's memory is separate. Every request is checked against the key.

Reading someone else's content can change what the agent is allowed to do next. An email to an address the person never gave waits for the person's yes after the agent read someone else's content. You set this under Actions > Automation > Permissions. See [Permissions](/docs/agent-harness/permissions).

## Reauthorizing

To ask a person to approve again, use the reauth link from `GET /v1/context-sources/{provider}/reauth-url`. The person opens the link and approves.

## Next

- [Agent harness overview](/docs/agent-harness/overview)
- [Permissions](/docs/agent-harness/permissions)
- [Memory API overview](/docs/memory-api/overview)