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

# Set up your organization

> A checklist for admins standing up Deal Brain for a team.

This is the admin path — you're building the foundation the rest of your team works on top of. If you're a seller getting started, go to [Getting Started](/using/getting-started) instead.

Work through these in order. Each step builds on the one before it, and you can check your progress at any point:

```text wrap theme={null}
Show me our Deal Brain instance setup. What's configured, what's blocked, and what should I do next?
```

Deal Brain reports readiness per capability along with specific blockers and the next step for each.

## 1. Connect your context sources

Start here — everything else depends on Deal Brain having context to work with.

<Steps>
  <Step title="Connect a source of opportunities">
    Connect [Salesforce](/integrations/salesforce) or [HubSpot](/integrations/hubspot) as your system of record. If you can't get admin approval yet, a [CSV import](/integrations/csv-import) gets your team running today and you can connect a CRM later.
  </Step>

  <Step title="Connect Google Workspace">
    [Gmail and Calendar](/integrations/google) give Deal Brain the email and meeting context that powers briefs and drafts.
  </Step>

  <Step title="Connect a transcript source">
    [Granola](/integrations/granola), [Gong](/integrations/gong), or [Fathom](/integrations/fathom). Transcripts are the highest-value context Deal Brain ingests.
  </Step>

  <Step title="Connect Slack and Notion">
    [Slack](/integrations/slack) for deal-channel context, [Notion](/integrations/notion) for deal plans and account notes. Both optional, both meaningful.
  </Step>
</Steps>

## 2. Add playbook sources

Without these, Deal Brain gives good generic sales advice. With them, it gives *your* advice.

Start with one `sales_process` source — it unlocks the synthesized process overview and answers the questions your team asks most. See [managing sources](/playbook/sources).

## 3. Define signals

Pick the two or three patterns your team already tracks by hand and turn them into [signals](/signals). Preview before activating, then backfill over a narrow window first.

Resist defining ten at once. Two good signals beat ten noisy ones.

## 4. Publish canvas templates

[Canvas templates](/canvas) give your team consistent document structure — pipeline reviews, deal one-pagers, meeting briefs. Agents can post them directly to Slack.

At least one published public template is needed before agents can use canvas content.

## 5. Configure agents

Once the above is in place, [agents](/agents) can act on it. Start with a single team agent posting a weekly pipeline summary, and expand from there.

## 6. Get your team connected

Each seller connects their own AI platform:

<CardGroup cols={3}>
  <Card title="Claude" icon="sparkles" href="/integrations/claude">
    Setup guide
  </Card>

  <Card title="ChatGPT" icon="comments" href="/integrations/chatgpt">
    Setup guide
  </Card>

  <Card title="Other tools" icon="plug" href="/integrations/mcp">
    Any MCP client
  </Card>
</CardGroup>

Then point them at [Getting Started](/using/getting-started) for prompts that work on day one.

## Permissions

Configuration is permission-gated. Depending on your role you may have some or all of:

| Permission           | Grants                                |
| -------------------- | ------------------------------------- |
| `configure_canvas`   | Create and publish canvas templates   |
| `configure_signals`  | Define, preview, and activate signals |
| `configure_agents`   | Create and enable team agents         |
| `configure_playbook` | Add and approve playbook sources      |

If a capability looks missing rather than blocked, it's usually a permissions question. Deal Brain reports what actions you're allowed to take — don't infer permissions from what you can't see.

## Checking readiness later

The setup check is worth re-running after any significant change:

```text wrap theme={null}
Re-check our instance setup and list any new blockers.
```