Skip to main content
The template field editor is the same canvas and palette as a package’s field editor, with one difference: fields are assigned to a role (from the template’s Roles section) instead of a named recipient, since the actual people are only chosen when the template is used to send a package or bulk send.

Video guide: Adding template fields

The template field editor with the document canvas and field toolbarThe template field editor with the document canvas and field toolbar

The template field editor, the same canvas a package uses.

Document tabs across the top switch between the template’s documents. Dynamic documents (Word files that adapt to each send) don’t appear here, because fields are placed on rendered PDF pages. Documents linked from the library aren’t shown either: their fields are edited in the library and belong to the template roles chosen in Choose roles (see Linked documents). A selector under Role picks which role’s fields you’re placing. Roles that only receive the document (viewers and CC) are not offered for fields. Roles can be managed here too. Add role opens a small form with Role name, Recipient type and Delivery. Each role’s three-dot menu has Edit role and Remove role. A template has between one and 10 roles, and two roles can’t share a name. Adding, editing or removing a role here is saved straight away, separate from Save fields. Removing a role deletes its fields on every document in the template, so it asks you to confirm first. The removal can’t be undone. A role that a merge field reads from can’t be removed: choose another role for that merge field first. Save your changes before removing a role. A role used in the workflow has to be taken out of the workflow before it can be removed, and its name and type are changed in template setup. A role that already has fields can’t be switched to view only until they are removed or reassigned. Conditional logic works the same way here, with each rule’s fields tied to one role. Rules carry through to every package sent from the template (single or bulk) and to duplicates of it, and a rule can’t link fields that belong to two different roles. Your changes save automatically shortly after each edit, and again before you leave. Save fields (or Ctrl+S, Cmd+S on a Mac) saves straight away. If a save failed, leaving asks first and offers Save fields & continue. Preview saves any unsaved fields before it opens, so the preview always shows your latest placement. Publish (or Publish changes on a published template) saves, checks the template and opens the same publish dialog as the template builder. A document with no signing fields reads No signing fields there. If something still needs fixing, it takes you to the document or builder section at fault. After publishing, Done takes you to All Templates. Back to template returns to the template builder.