> ## 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.

# Managing sources

> Add, tag, approve, and maintain the knowledge Deal Brain sells from.

Managing sources requires the `configure_playbook` permission.

## Two ways to manage sources

You can manage playbook sources in the Deal Brain web app or over MCP from a connected AI platform. Both reach the same sources.

* **Web app** — click **Playbook** in the left sidebar to open `/app/dashboard/playbook`. Click **Upload Artifacts**, top right, to add a source. Use this surface for files — MCP accepts pasted text only. The page has **Overview** and **Artifacts** tabs.
* **MCP** — describe what you want in plain language. Use this for content you can paste as text, and when an agent is doing the configuring. The rest of this page follows this path, because every step is one prompt.

## Add a source

```text wrap theme={null}
Add a playbook source called "MEDDPICC stage criteria". Perspective is sales_process, domains are methodology and process. Here's the content: [paste]
```

Content can be up to 500,000 characters, so full methodology documents are fine.

Over MCP you paste content as text. To add a source from a file, use **Upload Artifacts** in the web app instead.

## Tag it well

Perspective and domains determine when Deal Brain reaches for a source. Getting them right matters more than the content being perfectly written.

| If the source is…                        | Perspective                   | Likely domains           |
| ---------------------------------------- | ----------------------------- | ------------------------ |
| Your stage definitions and exit criteria | `sales_process`               | `process`, `methodology` |
| Rep-facing "how we sell" guidance        | `seller_playbook`             | `methodology`, `rules`   |
| Product capability reference             | `product_reference`           | `product`                |
| A competitive battlecard                 | `competitor_reference`        | `product`, `company`     |
| A competitor's own website copy          | `competitor_self_description` | `company`                |
| Company story and positioning            | `company_reference`           | `company`, `voice`       |
| Analyst or market research               | `market_research`             | `company`, `product`     |

Set the **subject** when a source is about a specific entity — a named competitor, a particular product line. It's how Deal Brain tells two competitor sources apart.

## Approve it

Processing runs first, then you approve:

```text wrap theme={null}
Show me pending playbook sources and their processing status.
```

```text wrap theme={null}
Approve the "MEDDPICC stage criteria" source.
```

Approve only after processing completes. Until then, the source isn't used.

## Update a source

```text wrap theme={null}
Update the content of "MEDDPICC stage criteria" with this revised version: [paste]
```

**This clears approval and restarts processing.** The source stops being used until you approve it again — which is the point. It stops approved content being silently replaced.

Same applies to changing perspective, domains, subject, or title.

## Reprocess

If processing failed, or you think extraction missed something:

```text wrap theme={null}
Reprocess the "MEDDPICC stage criteria" playbook source.
```

Admins can see failed sources; members can't. If your team says a process question isn't answering, check for failed sources first.

## Delete

```text wrap theme={null}
Delete the "Old 2025 playbook" source.
```

Soft delete. It stops being used immediately.

## Concurrent edits

Sources carry a revision. If someone else edits a source between your reading it and writing it, your change is rejected. Re-list to get current state and reapply.

## What good coverage looks like

You don't need everything on day one. In rough priority order:

1. **One `sales_process` source.** Unlocks the synthesized process overview and answers the most common questions.
2. **A `seller_playbook` source.** How your team is expected to run deals.
3. **`product_reference`.** Stops Deal Brain guessing at your capabilities.
4. **Competitor sources**, as they come up in real deals.
5. **`company_reference` with the `voice` domain.** Improves drafts noticeably.