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

# Integrations

> Connect cf0 to the tools your firm already uses — Microsoft 365, Google Workspace, Slack, Notion, Granola. Data flows into Lab automatically.

Integrations let your firm's existing tooling become a queryable source inside cf0. Once connected, cf0 reads from these sources continuously — so when an analyst asks about a customer in Lab, the answer can pull from the Slack thread last week, the Notion deal page, the Gmail introduction from the founder, alongside the SEC filings.

## Available integrations

cf0 ships with five connector groups. Set them up under **Settings → Integrations** (org admin only).

<CardGroup cols={2}>
  <Card title="Microsoft 365" icon="briefcase">
    Outlook, OneDrive, SharePoint. Firm email and shared documents become searchable.
  </Card>

  <Card title="Google Workspace" icon="folder">
    Gmail and Google Drive. Customer comms and shared docs flow into cf0.
  </Card>

  <Card title="Slack" icon="message-square">
    Channels you opt in to. Decisions, deal threads, and customer signal become structured context.
  </Card>

  <Card title="Notion" icon="book-open">
    Internal wikis, CRM pages, deal memos. cf0 reads page content and tracks updates.
  </Card>

  <Card title="Granola" icon="mic">
    Meeting transcripts. Calls with prospects, customers, and your team become queryable.
  </Card>
</CardGroup>

## Connect an integration

<Steps>
  <Step title="Open Settings → Integrations">
    Org admin role required. Non-admins see the catalogue but cannot connect new sources.
  </Step>

  <Step title="Click Connect on a toolkit">
    Each connector opens its OAuth flow in a new window. Sign in with the relevant account and grant cf0 the requested scopes.
  </Step>

  <Step title="Choose scope">
    For tools with granular access (Slack channels, Notion workspaces, Google Drive folders), pick exactly what cf0 should read. Default to "least privilege" — start narrow, expand once you trust the surface.
  </Step>

  <Step title="Verify ingestion">
    Once connected, cf0 begins reading the source within minutes. Watch the **Data activity** indicator at the bottom of the Integrations panel for first-pass progress.
  </Step>
</Steps>

## What cf0 does with integration data

Connector data is structured and joined to SEC filings, transcripts, and uploaded documents. From an analyst's perspective in Lab, there is no separation — a question like *"What did the founder of \$TICKER say about Q4 guidance, and how does it compare to the public 10-Q?"* can pull from a Granola meeting transcript, a Slack thread, and the actual filing in a single answer.

cf0 tracks **provenance** for every fact: which integration it came from, when it was last updated, and the conversation or document it originated in.

## Scope and privacy

* **Org-scoped**: connections live at the organisation level. Every member of the org sees data from connected sources in Lab (subject to your firm's own access policies in the underlying tool).
* **No training**: cf0 never uses your connected data to train any model.
* **Revocable**: disconnect any integration at any time from the same panel. cf0 stops reading from that source immediately; previously ingested data is purged on the next sync cycle.

## Documents path (for content not in a connector)

If you have material that doesn't live in one of the supported tools — a pitch deck, a one-off PDF, a CSV from your data vendor — upload it directly via [Documents](/features/documents). It joins the same Lab context as connector data.