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

# Updates

> Review, approve, and reject the CRM field updates Deal Brain proposes from your meetings, email, and chats.

Updates is the queue where you review CRM changes Deal Brain wants to make. It's the second item in the left sidebar of the web app, at `/app/dashboard/updates`.

Deal Brain reads your meetings, email, and other connected sources, and proposes new values for the fields it tracks on your opportunities. Those proposals wait here until you approve or reject them.

## Where updates come from

Each field has its own update mode, and the mode decides whether the field ever reaches this queue:

| Update mode   | Shows up in Updates?                                                                   |
| ------------- | -------------------------------------------------------------------------------------- |
| **Suggest**   | Yes. The proposal waits here for your review. Nothing is written until you approve it. |
| **Automatic** | No. Deal Brain writes the value to your CRM without a human review step.               |
| **Manual**    | No. Deal Brain generates no proposals for the field at all.                            |

[Fields and CRM objects](/admin/fields) is the authority on update modes, including how to change one and who can change it. If a field you expected to see never appears in this queue, that page is where to start.

## The queue

The page has three tabs:

* **Pending** — proposals waiting on you, with a count badge showing how many there are.
* **Approved** — proposals you've already accepted.
* **Rejected** — proposals you've turned down.

Use the **Find an update** box to search the queue, and **Reject All** and **Approve All** at the top right to act on the queue in bulk.

Updates are grouped by date under headings like **Yesterday**, **Monday, August 3**, and **Friday, July 31**, so the most recent context is at the top.

### Reading a collapsed update

Each row in the list is one update — a set of proposed field changes on a single opportunity. Before you expand it, the row tells you:

* **A count badge** — how many proposed field updates the update contains.
* **The opportunity name**, with the account name beneath it. For example, an opportunity on the Acme account.
* **Source icons** — small marks showing where the underlying context came from, such as Granola, Gmail, Slack, or Notion.
* **A timestamp** — reading "as of" a date and time, so you know how current the proposal is.

## Reading an update in detail

Expand a row to see a table of the proposed changes, one row per field:

| Column              | What it shows                                                                                                                                     |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Checkbox            | Selects the field row.                                                                                                                            |
| **Field**           | The field being updated.                                                                                                                          |
| **Proposed Update** | The value Deal Brain wants to write.                                                                                                              |
| **Show current**    | Reveals the value currently in your CRM, so you can compare before deciding.                                                                      |
| **Reason**          | Prose explaining why Deal Brain is proposing the value, with a numbered citation marker and a badge naming the integration the context came from. |

Always check **Show current** before approving. A proposal that looks correct on its own may still be worse than what's already in the field.

The **Reason** column is what makes a proposal auditable. If a proposed champion on the Jaffle Inc opportunity looks wrong, the citation and source badge point you back to the meeting, message, or email that produced it.

There's also a **Quick Add** control at the bottom of an expanded update.

## Approving and rejecting

Each expanded update has a row of action icons in its top right corner. Approve and reject are among them.

* **Approve** writes the proposed values to your CRM.
* **Reject** discards them, and the update moves to the **Rejected** tab.

### Acting in bulk

**Approve All** and **Reject All** at the top right apply to the queue rather than a single update. **Approve All** writes every pending proposal to your CRM in one action, across every opportunity in the queue — including proposals you haven't opened or compared against their current values. Reach for it only when you've already reviewed what's there, or when the queue is small enough to take in at a glance.

## Approved and rejected history

The **Approved** and **Rejected** tabs are your record of what you decided. Use them to check whether a value reached your CRM, or to see what Deal Brain proposed on a deal and what happened to it.

## When an integration needs reconnecting

A warning banner can appear at the top of the page — for example, **Reconnect Granola**, with the explanation that one or more integrations need to be reconnected before Deal Brain can resume syncing source data, and a **Reconnect** button.

This is how a broken integration surfaces to you. Until you reconnect it, Deal Brain stops syncing data from that source, so no new context flows in and no new proposals are generated from it. The queue quietly goes stale: what's in front of you still reflects the last successful sync, not what's happened since.

Click **Reconnect** and re-authorize the source. Treat the banner as urgent — the longer it sits, the further your CRM drifts from what your calls and email actually say.