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

# Integrations overview

> Connect the tools your projects use and let Brink answer across them with citations

Brink connects to the systems your team already works in — project management, email, chat, calendars, and file storage — and indexes their content so the assistant can answer questions with citations back to the original source.

## How integrations work

There are three concepts to understand, and they build on each other:

<Steps>
  <Step title="Connect an account">
    An **integration** is a type of source (Procore, Slack, Box, …). Connecting creates an **account** — an authorized link between Brink and that tool, established through the provider's own sign-in and consent screen. Brink never sees your password.
  </Step>

  <Step title="Bind resources to projects">
    A **scope binding** maps one external resource — a Procore project, a Slack channel, a Box folder, a mail label — to one Brink project. **A connected integration with no binding delivers nothing**, so this step is not optional.
  </Step>

  <Step title="Sync">
    Once bound, Brink backfills history and then keeps the source in sync automatically. You can also trigger a sync manually at any time with **Sync now**.
  </Step>
</Steps>

<Warning>
  Connecting is not enough on its own. After you connect an account, bind it to a project on the **Projects** page (or the Integrations page's Projects tab) — nothing syncs until a binding exists.
</Warning>

## Organization vs. personal connections

Every integration connects in one of two modes:

* **Organization connections** are set up by an **owner or admin** from the **Integrations** page. The data is shared with the projects it's bound to.
* **Personal connections** are set up by any member from **Profile → My integrations**. Data from a personal connection is **only visible to you** — it powers your own assistant and is never shared with your team.

Some integrations support only one mode. Gmail, for example, is personal-only — a mailbox belongs to one person — so it never appears on the organization tab. Connect it from your profile instead.

## Available integrations

| Integration                                          | Category           | Who connects                 | Bind to         |
| ---------------------------------------------------- | ------------------ | ---------------------------- | --------------- |
| [Procore](/integrations/procore)                     | Project Management | Org admin                    | Procore project |
| [Gmail](/integrations/gmail)                         | Communication      | Personal only                | Gmail label     |
| [Outlook](/integrations/outlook)                     | Communication      | Org admin or personal        | Mail folder     |
| [Google Calendar](/integrations/google-calendar)     | Communication      | Org admin or personal        | Calendar        |
| [Outlook Calendar](/integrations/outlook-calendar)   | Communication      | Org admin or personal        | Calendar        |
| [Slack](/integrations/slack)                         | Communication      | Org admin                    | Public channel  |
| [Microsoft Teams](/integrations/microsoft-teams)     | Communication      | Org admin                    | Team + channel  |
| [Box](/integrations/box)                             | Documents          | Org admin                    | Folder          |
| [Dropbox](/integrations/dropbox)                     | Documents          | Org admin or personal        | Folder          |
| [AI Employee Inbox](/integrations/ai-employee-inbox) | Communication      | Auto-provisioned per project | —               |

## Where to find things

* **Integrations page** (`Integrations` in the sidebar) — browse the catalog, connect organization accounts, see sync status, and manage each connection from its drawer.
* **Profile → My integrations** — connect and manage your personal accounts.
* **Projects page** — each project card has an **Integrations** tab where you bind resources and trigger per-binding syncs.
* **Onboarding** — the setup wizard's *Connect your tools* step offers the organization-level integrations when you first create your org.

## Who sees what

Brink resolves visibility for every piece of ingested data, in strict order:

1. **Private** — anything from a personally connected account is visible only to that person. No setting can widen it.
2. **Project-scoped** — data bound to a project is visible to that project's members.
3. **Organization-wide** — shared, non-mail sources with no project binding.

Mail and calendar sources (Gmail, Outlook, Google Calendar, Outlook Calendar) get extra protection: if Brink cannot determine whose mailbox a connection represents, the data is held unreadable by anyone rather than defaulting to org-wide. The system fails closed — a lookup failure never publishes a mailbox to the whole company.

See [Syncing & permissions](/integrations/syncing) for sync cadence, status indicators, and troubleshooting.

<Note>
  If a provider's OAuth app hasn't been configured for your deployment yet, clicking **Connect** creates a **demo connection** seeded with sample data (you'll see account names like `demo-*` and resources like "Demo Tower"). Contact Brink to enable the real connection.
</Note>