Skip to main content
The field editor opens from Edit document fields in the package creator, or from a draft’s Continue to fields button. It is only available while the package is a draft (or while you are correcting it). It shows your documents on a canvas with a field palette, a signer selector and a properties panel, with a tab for each document.

Video guide: Placing signature fields

A document linked from the library has no tab here, because its fields are edited in the library. Use Detach to customise on its card in the package creator to place fields on it here instead. See Linked documents.
The field editor with the document canvas and the field toolbarThe field editor with the document canvas and the field toolbar

The field editor, placing fields on a draft's documents.

Signer selector

Under Signer, choose which recipient you are placing fields for. Each recipient’s fields are colour-coded, so you can see at a glance who owns what across the document. Only recipients who sign are offered: viewers and CC recipients can’t be given fields. If there are no signers yet, add a recipient first.

Field palette

Drag a field type onto the page. Available types:
  • Signature: Signature, Initial.
  • Auto-fill (filled automatically from the recipient’s details): Date signed, Name, Email, Company, Title.
  • Input: Text, Number, Checkbox, Radio, Dropdown.
Drag a placed field to move it, drag its handles to resize it, and select multiple fields with a marquee selection or Shift-click. If a PDF already contains form fields, an Import form fields button appears. Click the form fields you want to bring in, then Import.

Properties panel

With a field selected, Field properties edits its settings, for example whether it is Required, its data label, placeholder text, or the options for a dropdown. If the panel is collapsed, selecting a field opens it. Radio buttons have two extra settings:
  • Radio group: buttons with the same group name act as one question, so the signer can pick only one of them.
  • Option name: what this option means, like Yes or No. It names the answer in conditional logic and in exports.

Conditional logic

Conditional logic shows, hides or requires a field depending on the signer’s answer. A checkbox, a radio group or a dropdown is the question. Each of its answers has its own card in the Conditional logic part of Field properties. For a radio group or dropdown the card reads like “If Yes is selected”. For a checkbox it reads “If the box is Checked” or “If the box is Not checked”. Hover an answer to see what it means for the signer.

Setting it up

  1. Select the question field.
  2. On an answer’s card, select the dashed Add field button and choose Show a field, Hide a field or Require a field. A banner appears above the page.
    The Add field menu open with Show a field, Hide a field and Require a fieldThe Add field menu open with Show a field, Hide a field and Require a field

    Choosing what an answer does to a field.

  3. Click the fields on the page that the answer should show, hide or make required.
  4. Select Done (on the card or the banner) to save the rule, or Cancel on the banner to leave it unchanged.
Only fields for the same signer can be picked. Picking a radio button brings its whole group with it. Rules can chain (a field shown by one answer can itself be a question), up to 5 levels deep.
The field editor with the picking banner showing above the page and fields being selectedThe field editor with the picking banner showing above the page and fields being selected

Picking the fields to show for an answer.

Reviewing and changing rules

A card with fields turns blue and lists them under Show these fields, Hide these fields and Require these fields, each with a count. Edit, next to each heading, picks that list’s fields again. Clear, in the card’s three-dot menu, removes them all. Undo brings a cleared rule back. Click a field in the list to scroll to it on the page: it pulses briefly but isn’t selected.
The Field properties panel showing the Conditional logic cards for each answer, one of them blue with its field countThe Field properties panel showing the Conditional logic cards for each answer, one of them blue with its field count

Field properties, with a card for each answer.

Fields with logic show a small branch badge on the page. Hover it to read the rule, for example “Shows when Consent is checked”. The rule starts with Shows when, Hidden when or Required when. Selecting a conditional field shows a card that reads “If Consent / is Checked”, then the field itself under Show this field, Hide this field or Require this field. The card’s three-dot menu has Go to question, to jump to the question field, and Clear, to remove the rule. If the question was deleted, the card says the field always shows instead, with Clear logic to tidy it up.

Previewing

Preview is the full-width button under the cards, on a question or on a field with logic. It shows the page as the signer would see it for one answer. A red-outlined banner, centred over the page, reads “Previewing” and the question’s name, with a button for each answer to switch between them. Fields that won’t show are dimmed with a dashed outline, and fields an answer reveals briefly pulse. Fields can’t be edited while previewing. Select Exit preview or press Esc to return to editing.
The field editor previewing one answer, with the red-outlined preview banner and a hidden field dimmed with a dashed outlineThe field editor previewing one answer, with the red-outlined preview banner and a hidden field dimmed with a dashed outline

Previewing an answer. The field it hides is dimmed.

Testing logic

The flask button in the toolbar (Test logic) lets you answer the questions on the page yourself and watch fields show, hide or become required. Field properties closes while you preview or test. Nothing you enter is saved. Reset answers clears what you’ve entered, and Exit test (or Esc) returns to editing. The button is disabled, with the tooltip “Add logic to a field to test it”, until at least one field has a rule.

Hidden fields and warnings

Hidden fields are never required and leave nothing on the signed PDF. Anything a signer typed into a field that ends up hidden is discarded. Fields start out Required, so for a require rule to matter, untick Required on the field first. The field is then optional until its answer is given, and must be completed before the signer can finish. Deleting a question asks first, because its fields would then always show. Changing a field’s signer so that a rule would cross signers also asks first, and removes that rule. Saving is refused for a rule that links two signers, creates a loop, chains more than five levels deep, or makes a radio button depend on its own group. Rules that stop making sense (the question or the chosen option is deleted, or the question moves to another signer) are cleared, so the field always shows. Rules are kept when a package is duplicated or corrected, and when it is sent from a template.

Saving and sending

Your changes save automatically shortly after each edit, and again before you leave the editor. Save fields (or Ctrl+S, Cmd+S on a Mac) saves straight away. You are only asked before leaving if a save failed: the dialog says Your latest changes haven’t saved yet. and offers Save fields & continue, Discard and Keep editing. Back to edit returns to the package details. Preview shows the package as recipients will see it. If a signer has no signature or initials field, the send confirmation warns you first. You can still send. Activate package sends it, and its menu also offers Schedule send and Sign in person. Sign in person is available when a recipient’s delivery is In person and you are their host. Otherwise it is disabled, with a tooltip saying why.