Custom fields
Define typed custom attributes for contracts—text, numbers, dates, yes/no, email, URL, or dropdowns—and use them on contract detail and in views.
Custom fields (custom attributes) let you store organization-specific data on every contract—examples include Region, Risk tier, Budget code, Business owner, or Renewal owner.
Where to manage them
Go to Admin → Contract Management tab → Manage Custom Fields (opens the Custom Fields panel).
The panel explains that you can create custom fields to store additional information on your contracts.
Creating or editing a field
- Click Add Custom Field (or edit an existing row).
- Display name (required) — the label users see. For new fields, the app derives an internal name from this (for example,
Contract Value→contract_value). When editing, the internal name is kept as-is. - Description — optional help text. The model treats this as describing what the field means (including for AI-related workflows where the description is used).
- Data type — choose one of the types below.
- For Dropdown, add one or more choices; you cannot save a dropdown without at least one option.
- Create or Update to save, or Cancel to discard.
Active fields
The list shows your definitions (count of active fields). You can edit or remove fields from here. Deactivating or changing types/options can affect existing contract values—pilot changes on a few records before rolling out broadly.
Available data types
When you pick Data type, these options are available (labels as shown in the product):
| Data type (UI) | Stored as | Best for |
|---|---|---|
| Text | Free-form string | Short labels, notes, codes, multi-word values. |
| Number | Numeric values | Amounts, scores, counts (the backend can support min/max validation where configured). |
| Date | Calendar date | Deadlines, review dates, fiscal milestones. |
| Yes/No | Boolean | Flags such as “Requires legal review” or “Strategic account.” |
| Email address | Contact emails tied to the deal. | |
| URL | Web link | Links to systems of record, folders, or tickets. |
| Dropdown | One of a fixed list | Controlled vocabulary (e.g. Low / Medium / High risk). You maintain the list of options in the field definition. |
Dropdown fields require at least one choice before you can save.
How they’re used
- Contract detail — Values appear where your layout places custom attributes (often grouped with other metadata). Users who are allowed to edit can update values inline, subject to permissions.
- Contract views — Custom fields can be added as columns and used in filters and sorting so teams can work from the same structured data.
- Chat and analysis — Descriptions and values can feed workflows that use contract metadata (for example, when full-text storage and analysis are enabled for your org).
- Reporting / exports — Depending on your setup, custom field columns may be included when you export or analyze contract tables.
End-user labels for system fields (and sometimes how columns read) may be overridden under Settings → Field label customization / Customize Labels when that feature is enabled—custom fields still use your display names unless you align naming there.
Tips
- Prefer Dropdown when you need consistent reporting; use Text when values are truly open-ended.
- Use Description so future admins and AI-assisted flows understand what the field means.
- Email and URL encourage valid formats compared to plain text.
Data and integrations
Custom field values live in Contracts AI. They are not automatically synced from external systems unless an integration or import path maps into those attributes—confirm with your admin for your org’s setup.
Did this answer your question?