Configure fields
After adding fields to a template, you can configure each field to control who completes it, how it behaves, and what information it should collect.
Field configuration helps make sure the template is ready for different signing situations and that each signer sees and completes the fields intended for them.
Field properties
Select a field in the template editor to view its properties in the Fields & Properties panel.
The available properties depend on the type of field you have selected. Common properties include:
| Property | What it controls |
|---|---|
| Recipient | Determines which signer is responsible for completing the field. |
| ID (Slug) | A unique identifier for the field. This is useful when referring to fields through integrations or other system processes. |
| Name | The name used to identify the field. |
| Placeholder | Optional guidance displayed inside an empty input field. |
| Width / Height | Controls the size of the field on the document. |
| Required Field | Determines whether the signer must complete the field before they can submit the signing request. |
Different field types may have additional properties specific to their purpose.
Assign fields to the right signer
The Recipient property determines who completes a field.
For example, if a template has two signer roles, Customer and Company Representative, the customer's signature field should be assigned to Customer, while the company's signature field should be assigned to Company Representative.
When the template is used in a signing request, actual people are assigned to these signer roles.
See Add Signers.
Make a field required
Enable Required Field when the signer must provide a value before they can submit the signing request.
For example:
- A signature field will normally be required.
- A customer's phone number may be required if your process needs it.
- An optional comments field can be left as not required.
Required fields cannot be skipped during signing.
Field size and placement
Width and Height determine how much space the field occupies on the document.
Adjust these values when necessary to make the field fit the area where the signer is expected to enter information.
You can also reposition fields directly on the document. Visible guide lines help you align fields accurately with the underlying document content.
See Add Fields.
Field IDs and names
Each field has an ID (Slug) and a Name.
The ID provides a unique identifier for the field, while the Name makes the field easier to understand when working with the template and its configuration.
For example:
ID: customer_name
Name: Customer Name
Using clear and meaningful names makes templates easier to manage, particularly when they contain many fields.
Prefill information
Some fields can be populated by the sender before a signing request is sent.
For example, an Event Waiver template can contain a Venue field. When creating a signing request, the sender can prefill it with Boston for one event and New York for another, while continuing to use the same template.
See Prefill Fields.
Before you finish
Before saving a template, review each field and check:
- Recipient: Is the correct signer assigned?
- Required Field: Should the signer be required to complete it?
- Name and ID: Are they clear and meaningful?
- Size and position: Does the field fit correctly on the document?
- Prefill: Is this information something the sender will provide before sending?
Once the fields are correctly configured and the required signing setup is complete, the template can be used as a Fillable template for signing requests.