This article explains how to create, configure, and use custom data properties to extend your document capabilities beyond the standard fields.
What is Custom Data?
Custom Data enables you to define and use your own document properties as a complement to the default properties that all documents have (such as company name, document title, and creation date).
Instead of being limited to standard document fields, you can create custom properties like Project ID, Purchase Order Number, Department, Industry Type, or any other data points relevant to your workflow.
Why Use Custom Data?
The default document properties don’t cover every business need. Custom Data solves this by letting you define exactly the fields you need.
Key Benefits:
Better Organization: Filter and search documents using criteria relevant to your business.
Improved Workflow: Set up conditional logic based on your custom properties.
Enhanced Tracking: Monitor documents by project, department, or other custom categories.
Flexible Data Management: Adapt the system to your unique business requirements.
Supported Field Types
When creating a custom data field, you can now choose from:
Text fields – for names, industries, IDs, or free text values.
Number fields – for numeric values like “Number of licenses = 250.”
Yes/No fields – for simple choices like “Auto-renewal = Yes/No.”
These field types make it easier to sync with CRM fields and create smarter conditional content.
Custom Data Capabilities
Custom Data includes three main functionalities:
Custom Data Settings – Configure what properties can be used on documents, templates, and rooms.
Conditional Logic – Set conditions based on your custom fields to show or hide content dynamically.
Filter & Search – Search and filter documents in Contract Management using your custom fields.
Setting Up Custom Data Properties
Creating Custom Properties
Navigate to your Entity Settings.
Select Custom Data from the menu.
Click Add Custom Data.
Configure the field:
Label: Choose a descriptive name (e.g., Project ID).
Key: One word, starting with a letter (e.g., project_id).
If mapping to CRM fields, use merge tags like
custom.project_idorcustom.industry.Remove curly brackets when configuring.
Field Type: Select Text, Number, or Yes/No.
Adding Custom Data to Templates
Create or edit a template.
Access the Document Properties section.
Add your custom data fields.
When documents are created from this template, those fields will be available for use.
Setting Custom Data Values
During Document Creation: Enter values for your custom fields in the creation form.
Via CRM or API Integration: Automatically populate values using CRM fields or API calls.
Supported CRMs: Salesforce, HubSpot, Microsoft Dynamics, Upsales, Pipedrive.
Using Custom Data in Conditional Logic
You can show or hide content blocks based on your custom fields.
Steps:
Select the content element you want to control.
Open Conditional Logic settings.
Choose your custom field as the condition trigger.
Define the rule (equals, contains, greater than, yes/no).
Decide what happens when the condition is met.
Searching and Filtering with Custom Data
In Contract Management, you can filter and search documents based on your custom data values.
Steps:
Open the filter panel.
Select your custom fields.
Apply criteria to view documents that match.
Limitations & FAQ
Q: What field types are supported?
A: Text, Number, and Yes/No fields.
Q: Can I change the type of a field after it’s created?
A: No. Once created, the field type cannot be changed. All existing custom data fields created before this update are treated as Text fields. If you need another type, you’ll need to remove and re-create the field.
Q: Why does this matter for CRM integrations?
A: About 20% of CRM fields are numbers or yes/no values. Previously, these couldn’t sync into GetAccept. Now they can, making your contracts and automation much more powerful.
Q: Can I use Number and Yes/No fields in conditional content?
A: Yes, these fields can now drive conditional content, allowing you to automatically show or hide clauses based on CRM data.
Q: Does this work with all CRMs?
A: Yes, as long as the backend integration supports the field type (Salesforce, HubSpot, Microsoft Dynamics, etc.).
Summary
Custom Data Properties let you go beyond standard fields by adding Text, Number, and Yes/No fields that sync with your CRM, drive conditional content, and make documents easier to search and filter. This gives you smarter personalization, fewer templates to manage, and cleaner contract workflows.