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

# Fields and CRM objects

> Configure the fields Deal Brain tracks — scope, visibility, update behavior, frequency, and write mode — in Field Management.

Deal Brain syncs field definitions from your CRM for three object types: **opportunity**, **account**, and **contact**. Those fields are what it reads, reasons over, and updates.

You configure every one of them in **Settings → Field Management**.

## The Field Management page

Open the web app, go to **Settings**, and pick **Field Management** — the third item in the settings navigation, after **Profile** and **Team**, at `/app/settings/field-management`.

The page is a single table of every field Deal Brain knows about, one row per field:

| Column              | What it shows                                         |
| ------------------- | ----------------------------------------------------- |
| **Field Name**      | The field. Click it to open the **Edit field** panel. |
| **Category**        | `opportunity`, `account`, or `contact`.               |
| **Type**            | The field's data type.                                |
| **Scope**           | `Private` or `Team`.                                  |
| **Owner**           | Who the field belongs to.                             |
| **Managed By**      | `CRM` or `Deal Brain`.                                |
| **CRM synced**      | Whether the field syncs with your CRM.                |
| **Visible**         | Whether the field is shown.                           |
| **Update Behavior** | `Automatic`, `Suggest`, or `Manual`.                  |
| **Frequency**       | How often Deal Brain updates the field.               |
| **Write Mode**      | `Overwrite`, `Append`, or `Prepend`.                  |
| **Instructions**    | Free-text instructions for the field.                 |
| **Description**     | Free-text description of what belongs in the field.   |

A field name can appear more than once — once per category. `Account ID`, for example, exists separately as a contact field, an opportunity field, and an account field. Check the **Category** column before you edit, or you'll configure the wrong one.

### Categories and types

**Category** is the CRM object the field hangs off: `opportunity`, `account`, or `contact`.

**Type** is the field's data type. The types you'll see in the table include `reference`, `text`, `money`, `longtext`, `date`, and `boolean`. The full set Deal Brain reports across a field catalog also includes `number`, `datetime`, `select`, `percentage`, `multiselect`, `email`, `url`, and `phone`.

Fields carry your CRM's own naming, so what you see depends on which CRM you've connected. In Salesforce a MEDDPICC champion field appears as `Champion__c` and system fields like `CreatedDate` and `IsClosed` sync as read-only. In HubSpot you'll see property names like `dealtype` and `lifecyclestage`.

### Finding a field

Two controls narrow the table:

* **Find a field** — a search box at the top of the page.
* **Filters** — opens a panel that filters on **Field Name** (contains), **Category** (contains), **Type** (contains), **Scope** (checkboxes for **Private** and **Team**), **Owner** (contains), **Managed By** (checkboxes for **CRM** and **Deal Brain**), **CRM synced** (checkbox), **Visible** (checkbox), **Update Behavior** (contains), and **Frequency**.

The filters are how you audit policy across the whole workspace rather than field by field. Filtering **Update Behavior** to `Automatic` shows you every field Deal Brain writes without review — the single most useful view on this page before a security or governance conversation.

### Editing a field

<Steps>
  <Step title="Click the field name">
    The **Edit field** panel opens for that field.
  </Step>

  <Step title="Change the controls you need">
    The panel shows, in order: **Field Name**, **Scope**, **Visible**, **CRM synced**, **Update Behavior**, **Frequency**, **Write Mode**, **Instructions**, **Description**, **Owner**, **Category**, and **Type**.
  </Step>
</Steps>

Each control is covered below.

## Scope

**Scope** is either `Private` or `Team`. CRM-synced fields are `Team` by default, with an **Owner** of `Team`.

## Managed By

**Managed By** says where the field came from: `CRM` for fields synced from Salesforce or HubSpot, `Deal Brain` for fields Deal Brain holds itself.

## Visible

**Visible** is a toggle in the **Edit field** panel and a filter on the table. Every CRM-synced field observed had it on.

## CRM synced

**CRM synced** is a toggle in the **Edit field** panel and a filter on the table. Fields managed by your CRM have it on by default.

## Update Behavior

**Update Behavior** decides whether Deal Brain generates a proposal for the field at all, and whether a human has to approve the proposal before it reaches your CRM. There are exactly three options:

| Update Behavior | What Deal Brain does                                                                           |
| --------------- | ---------------------------------------------------------------------------------------------- |
| **Automatic**   | Writes the update itself, with no human review.                                                |
| **Suggest**     | Sends the update to the [Updates queue](/using/updates) for human review before it is written. |
| **Manual**      | Generates no proposals for the field.                                                          |

<Warning>
  Fields set to **Automatic** are written to your CRM with no human in the loop. Deal Brain does not pause for approval on those fields. Review which of your fields use **Automatic** before you describe Deal Brain's write behavior in a security or governance review.
</Warning>

In practice, identifier and system-ish fields sit on **Manual** — `Account ID` and `Closed` were both **Manual** on the fields observed — while substantive judgement fields like `Amount`, `Champion`, and `Close Date` sit on **Suggest**.

## Frequency

**Frequency** sets how often Deal Brain updates a field. Each option is one of two kinds, and the difference is the part worth getting right:

* **Since last update** measures from the moment the field itself last changed. A field that changed on Wednesday is next eligible a day, week, or month after Wednesday. The window is relative to the field.
* **A named reset** — start of day, a specific weekday, start of month — is a calendar boundary. Everything resets at the same moment for every field on that setting, regardless of when each field last changed.

Use *since last update* when you want a minimum quiet period after each change. Use a named reset when you want the whole workspace moving on the same cadence, like a Monday pipeline review.

| Frequency                       | Kind              |
| ------------------------------- | ----------------- |
| **Every change**                | Every change      |
| **Daily · since last update**   | Since last update |
| **Daily · start of day**        | Calendar reset    |
| **Weekly · since last update**  | Since last update |
| **Weekly · Sunday reset**       | Calendar reset    |
| **Weekly · Monday reset**       | Calendar reset    |
| **Weekly · Tuesday reset**      | Calendar reset    |
| **Weekly · Wednesday reset**    | Calendar reset    |
| **Weekly · Thursday reset**     | Calendar reset    |
| **Weekly · Friday reset**       | Calendar reset    |
| **Weekly · Saturday reset**     | Calendar reset    |
| **Monthly · since last update** | Since last update |
| **Monthly · start of month**    | Calendar reset    |

CRM-synced fields default to **Every change**.

## Write Mode

**Write Mode** decides what happens to the value already in the field when Deal Brain writes to it. There are exactly three options:

| Write Mode    | What happens to the existing value               |
| ------------- | ------------------------------------------------ |
| **Overwrite** | Replaced by the new value.                       |
| **Append**    | Kept, with the new value added to the end.       |
| **Prepend**   | Kept, with the new value added to the beginning. |

**Overwrite** is the default on every field observed. **Append** and **Prepend** suit long-text fields where the history matters more than the latest state — a running champion log rather than a single current champion.

## Instructions

**Instructions** is a free-text control in the **Edit field** panel. It was empty on every field observed.

## Description

**Description** is a free-text control in the **Edit field** panel, and a column on the table. It's the field's semantic guidance — what belongs in the field.

### Field descriptions do real work

A field's description isn't documentation — it's instruction. It tells Deal Brain what belongs in the field and, just as importantly, what doesn't.

A weak description produces noisy proposals. A strong one is specific about inclusion *and* exclusion:

> Stores the identity and specific internal influence actions of a single customer-side individual who actively advocates for the solution. Entries must document the individual's name and role alongside concrete evidence of how they exert political capital. **Excludes** individuals who solely perform administrative functions like vendor onboarding or procurement processing without clear demonstration of proactive internal sponsorship.

That exclusion clause is what stops every procurement contact getting logged as a champion.

## How CRM updates work

Every proposal Deal Brain generates cites the artifact it came from, whatever the update behavior, so you can trace a value back to the transcript, email, or saved chat that produced it.

### What happens on a Suggest field

<Steps>
  <Step title="Deal Brain observes something">
    A meeting transcript, email, or saved chat contains information relevant to a tracked field.
  </Step>

  <Step title="It proposes an update with citations">
    The proposal links back to the source artifact, so you can see exactly what it's based on.
  </Step>

  <Step title="You approve or reject">
    The proposal waits in the [Updates queue](/using/updates). Deal Brain writes nothing to your CRM for that field until you approve.
  </Step>
</Steps>

<Note>
  Only fields marked updateable can be written, in any mode. Read-only and system fields are never written.
</Note>

### Changing a field's update behavior

You set **Update Behavior** per field, so different fields on the same opportunity can behave differently. Changing it on a team field is an administrative action, not something every user can do.

## Inspecting your fields from chat

Field Management is where configuration happens, but you can read the same catalog from chat when you want a quick answer rather than a settings screen:

```text wrap theme={null}
List the opportunity fields Deal Brain is tracking. Which ones can it update?
```

Each field reports:

| Property           | Meaning                                                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field key**      | The CRM API name, e.g. `Amount`, `Champion__c`                                                                                                    |
| **Label**          | Human-readable name                                                                                                                               |
| **Data type**      | `text`, `longtext`, `number`, `money`, `percentage`, `date`, `datetime`, `boolean`, `select`, `multiselect`, `email`, `url`, `phone`, `reference` |
| **Updateable**     | Whether Deal Brain can write to it                                                                                                                |
| **Update mode**    | Whether the field is set to **Manual**, **Suggest**, or **Automatic**                                                                             |
| **Required**       | Whether your CRM requires a value                                                                                                                 |
| **Select options** | For `select` fields, the allowed values                                                                                                           |
| **Description**    | Semantic guidance for what belongs in the field                                                                                                   |

Don't hardcode field keys — list them and read what's actually there.

To see the full rules on a field, including value constraints and update policy:

```text wrap theme={null}
Describe the Champion and Economic Buyer fields in detail. What are the constraints and update rules?
```

And to see what's waiting on you:

```text wrap theme={null}
Show me pending CRM field updates across my deals, with the source for each one.
```

## Improving proposal quality

If proposals are noisy or missing, the field description is almost always the lever:

* **Too many proposals** → the description isn't excluding enough. Add what *doesn't* belong.
* **Wrong values** → the description isn't specific about format or source of truth.
* **No proposals** → the field may be set to **Manual**, its **Frequency** may not have come round yet, it may not be updateable, or nothing in your context speaks to it.

## Finding CRM records

```text wrap theme={null}
Find the account named Acme and list the contacts linked to its open opportunity.
```

For browsing pipeline rather than looking up records, ask about deals directly — Deal Brain has richer tools for deal triage than raw object listing.