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:
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.
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
1
Click the field name
The Edit field panel opens for that field.
2
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.
Scope
Scope is eitherPrivate 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:
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.
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:
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
1
Deal Brain observes something
A meeting transcript, email, or saved chat contains information relevant to a tracked field.
2
It proposes an update with citations
The proposal links back to the source artifact, so you can see exactly what it’s based on.
3
You approve or reject
The proposal waits in the Updates queue. Deal Brain writes nothing to your CRM for that field until you approve.
Only fields marked updateable can be written, in any mode. Read-only and system fields are never written.
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:
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:
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.