Custom fields

Custom fields enable you to capture document-specific information, such as purchase order numbers or contract start dates, that your team fills out on a per-document basis. Here's how to set them up and put them to work.

Accessing Custom Fields

Navigate to Settings > Custom Fields to find your list of existing fields and create new ones.

Proposify 2026-04-27 at 10.26.45 AM.jpg


Creating a Custom Field

  1. Go to Settings > Custom Fields
    Click to create a new field
  2. Enter a field name (e.g., "PO Number")
  3. Select a field type (currently Text Input, Date and Dropdown)
  4. Optionally, add placeholder text to guide your users (e.g., "Enter purchase order here")

Your new field will appear in your custom fields list, ready to be applied to a template.

Proposify 2026-04-27 at 10.35.27 AM.jpg
 

Applying a Custom Field to a Template

Custom fields are assigned at the template level, meaning you can have different fields on different templates: for example, a contract start date on your contract template but not on your proposal template.

  1. Open the template you want to configure
  2. In the sidebar, find Assigned Custom Fields
  3. Select the field you want to apply from the dropdown
  4. Save your changes

Note: You can't enter a value for a custom field at the template level - values are filled in at the document level when a document is created from that template.

Zight Recording 2026-04-27 at 10.40.12 AM.gif
 

Filling Out Custom Fields in a Document

When a document is created from a template with assigned custom fields, those fields are automatically inherited.

  1. Open the document
  2. Locate the custom field (e.g., "PO Number") in the document panel
  3. Enter the required value
Once filled in, the field value can also be used as a variable anywhere in the document body. Simply use the variable picker, navigate to the Custom Fields category, and insert the field. If the field hasn't been filled out yet, it will display as a placeholder until a value is entered.

A Practical Use Case

Custom fields are particularly useful for locked-down documents. For example, if you have a contract where you don't want sales reps editing the body copy, you can embed a custom field variable (like a contract start date) directly in the template. The sales rep simply fills in the field value, which populates the document automatically, without giving them access to edit anything else.
 

Custom Fields vs. CRM Variables

If you're coming from V2, you may have used custom fields to map data from your CRM. In V3, that's handled separately through CRM Variables, which let you pull any field or object directly from your CRM without needing to create a custom field first.
Custom fields in V3 are best used for information that doesn't come from a CRM: details you want your team to enter manually as part of completing a document or contract.

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section