Custom fields

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.

There are two kinds:

Kind	Scope	Where you manage it
Organization custom fields	Every contract in your org	Admin → Contract Management → Manage Custom Fields
View custom fields	One contract view only	Contract Views → view actions → Add New Field

Organization fields appear on contract detail and can be reused across views. View fields are created for a specific table view, populated in the background, and labeled (View Field) in column and filter pickers.

---

Where to manage organization custom fields

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

1. Click Add Custom Field (or edit an existing row).
2. 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.
3. Description — optional help text (up to 1,500 characters). Strongly recommended when using AI: the model uses this to understand what the field means during extraction and analysis.
4. Populate with AI — toggle (on by default). When enabled, Contracts AI can automatically extract and fill this field across contracts. When disabled, values are manual or integration-driven only; bulk AI extraction will not overwrite them.
5. Category (optional) — choose which contract detail tab displays the field: Overview, Parties & Locations, Term & Renewal, Financials, IP & Confidentiality, Data Security & Privacy, Legal & Compliance, or Other (default).
6. Data type — choose one of the types below.
7. For Dropdown:
   • Add at least two choices (required to save).
   • Optionally enable Allow multiple selections so users can pick more than one option.
8. Test before saving (new AI-populated fields only):
   • Expand Choose test contracts (optional) to pick sample contracts. The list shows your 10 most recent contracts; use search to find others.
   • Select up to 5 contracts, or leave none selected to test on the most recent contracts available (up to 5).
   • Click Test on ‘X’ Contracts to preview AI-generated values.
   • On the preview screen, review results per contract (including cases where no value was found). Click Save Field to create the field and run extraction on all contracts, or Refine Field to adjust the definition.
9. Skip testing — click Save Without Testing to create or update immediately, or Cancel to discard.

When Populate with AI is off, the test workflow and contract picker are hidden; use Save Without Testing (or Update when editing).

Active fields

The list shows your definitions (count of active fields). Each row displays the data type, whether it is Field populated by AI or Field not populated by AI, and for multi-select dropdowns a (multi) suffix.

You can edit or delete fields from here. Deactivating or changing types/options can affect existing contract values—pilot changes on a few records before rolling out broadly.

---

View custom fields (per-view)

From Contract Views, open a view you own and use the view actions menu:

• Add New Field — create a view-specific custom field (requires manage custom fields permission). Available types: Text, Number, Date, Boolean (Yes/No), and Dropdown. Description is required. Dropdown fields need at least two options; you can enable Allow multiple selections.
• Add Existing Field — add columns or filters from the shared catalog (standard contract fields, organization custom fields, and any view fields already on that view).

After you create a view field, analysis runs in the background. You can keep working; a notification appears when the field is ready and added to the view. View fields appear in the table and can be used in filters and sorting, labeled (View Field).

Only the view owner can add view custom fields.

---

Available data types

Organization custom fields (Admin)

Data type (UI)	Stored as	Best for
Text	Free-form string	Short labels, notes, codes, multi-word values.
Number	Numeric values	Amounts, scores, counts.
Date	Calendar date	Deadlines, review dates, fiscal milestones.
Yes/No	Boolean	Flags such as “Requires legal review” or “Strategic account.”
Email	Email address	Contact emails tied to the deal.
URL	Web link	Links to systems of record, folders, or tickets. Openable from contract detail when a valid URL is stored.
Dropdown	One or more values from a fixed list	Controlled vocabulary (e.g. Low / Medium / High risk). Enable Allow multiple selections for multi-value fields.

View custom fields

Same core types as above, except Email and URL are not available on view fields—use organization custom fields for those.

Dropdown fields require at least two choices before you can save.

---

How they’re used

• Contract detail — Organization custom fields appear on the tab you chose under Category. Users with edit contracts permission can update values inline. For AI-populated fields, hover a field card and use Re-analyze this field from the contract to refresh that single value from the document.
• Contract views — Organization custom fields and view custom fields can be added as columns and used in filters and sorting.
• Chat and analysis — Descriptions and values 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.

Users without permission to see a protected custom field may see it masked or hidden, depending on your organization’s access configuration.

---

Tips

• Prefer Dropdown when you need consistent reporting; use Text when values are truly open-ended.
• Use Description so admins, AI extraction, and view-field analysis all understand what the field means.
• Turn off Populate with AI for fields you will fill manually or via an integration.
• Use Category so fields show up on the right contract detail tab.
• For dropdowns that can have multiple valid answers (e.g. regions or tags), enable Allow multiple selections.
• Email and URL encourage valid formats compared to plain text.
• Test AI-populated fields on a few contracts before saving to all contracts.

---

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.

• Ironclad (and similar integrations) can map incoming source fields to organization custom fields. Fields with Populate with AI off are not overwritten when Contracts AI re-runs bulk extraction—useful for integration-sourced values.
• Confirm with your admin for your org’s integration setup.