---
title: Connect Google Docs
description: Connect your own Google Drive, add the Docs that define your decisions, and understand per-person access.
sidebar:
  order: 1
---

Your policy stays in Google Docs. Felspar reads it with **your own** Google access, keeps the exact version you add, and watches it for edits.

## Connect and add a Doc

1. Sign in at [app.felspar.ai](https://app.felspar.ai) and open **Sources**.
2. Under **Google Drive**, connect your Google account and approve access.
3. Click **Open Google Drive**. Google's own file picker opens in your browser.
4. Choose the Doc and click **Add**.

Felspar reads the Doc's current version, exports it as text, and stores it as a **source** with its own ID (`sourceObjectId`). The Doc now appears under **Added sources**, and Felspar starts watching it.

You need the **add sources** permission, which every member, approver and owner has.

## What Felspar can see

Felspar asks Google only for access to files **you pick** in the picker. It can't see the rest of your Drive. Each read uses a fresh, short-lived token for your connection; Felspar never stores or logs your Google token, and never uses someone else's connection to read a Doc for you.

Workspace roles grant no document access. Being an approver in Felspar doesn't let you read a Doc you can't open in Google.

## What counts as a Doc

- Native Google Docs only. Uploaded Word files and PDFs in Drive aren't read.
- If the Doc is edited while Felspar is reading it, the read is refused; try again.
- Every failure has a message: no connection, expired or revoked access, missing permissions, no access to the Doc, not a Doc, too large, empty, edited during the read, or Google unavailable.

## Per-person access

Some actions need the current person's own access to every Doc behind the pack, checked at that moment:

- reading a connected source;
- reading a proposal, approval or release built on one;
- proposing from a connected source;
- backtesting a proposal;
- approving and releasing.

If you don't have access, Felspar refuses with `source_access_required` and says only which provider and what is wrong (`not_connected`, `reconnect`, `missing_scopes`, `no_access`, `not_a_document` or `unavailable`), never the Doc's title. The Sources page hides titles of sources you can't open.

This is deliberate: nobody can approve a policy they can't read.

Running a released job doesn't need document access. Agents decide from the release, not from the Doc.

## Notion (beta)

You can also connect Notion and add pages. Notion support is in beta: Notion keeps an integration's access to a page shared with it even if you later lose access in Notion, so per-person checks are weaker than with Google Docs. Felspar reads the page's blocks up to three levels deep (up to 2,000 blocks), skips child pages and databases, and keeps nested headings as bold labels.

## Disconnect

On **Sources**, **Disconnect** removes your connection. Sources you already added stay, but Felspar stops watching them through your connection (their watch state becomes `stopped`). Reconnect to resume.

## Related

- [Source changes](/guides/source-changes): what happens when someone edits the Doc.
- [Draft a pack](/guides/draft-a-pack): turn the source into a pack.