Skip to main content
Templates & editor

Create and publish a template

Build a reusable template with parties, dynamic fields and settings, then publish it so your team can create documents from it.

Written By Sebastian

Last updated About 3 hours ago

A template is the master copy of a contract you use regularly. Everyone creates documents from it, fills in only what changes, and the rest stays exactly as approved.

Available on all plans · Owners, Admins and Editors create and publish templates

Create a template

  1. Open Create in the top bar and choose Create template.

  2. Enter a name.

  3. Choose how to start: upload a Word file, let the AI draft a first version, or start with a blank page.

  4. The template opens in the editor.

Let the AI draft a template

Instead of building a template by hand, let the AI draft it from an existing contract.

  1. Open the AI Assistant.

  2. Drag a Word (.docx) or PDF file into the chat.

  3. Ask it to create a template from the file, for example Create a template from this NDA.

The AI creates the template with dynamic fields, parties, party placeholders and signature blocks where they make sense. This takes a few minutes. Check the result, adjust it in the editor, then publish it.

Available to Editors and above. Uses AI credits, depending on the length and complexity of the document.

Set it up

Work through the right-hand panel from top to bottom:

  1. Parties: add a party for each side of the contract, such as "Company" and "Customer". In a template, a party is a placeholder: you only enter a reference, not the actual company. A template needs at least one party. See Parties and signatories in templates.

  2. Signature blocks: place them where the parties sign.

  3. Dynamic fields: add placeholders for everything that changes per contract, such as price or start date. See Dynamic fields: types, visibility, mandatory fields.

  4. Conditions (optional): show or hide clauses based on dynamic fields. See Conditions: show or hide content.

  5. Checkpoints (optional): require approval before review or signing. See Internal approvals with checkpoints.

  6. Attachments and file storage (optional): add fixed annexes such as your T&Cs. See Attachments, file storage and linked documents.

Template settings

SettingWhat it does
DescriptionShown when choosing a template, so colleagues pick the right one
Document typeDecides which metadata documents from this template get
Signature typeSimple, advanced or qualified electronic signature
Signing orderEnable sequential signing or let everyone sign at the same time. The default sequence follows signatory creation order; signatories defined in the template come first. An internal user can adjust the sequence in the document's Start signing dialog.
TeamsWho can use the template and see the documents created from it
TagsAdded to every document created from the template
Auto-accessUsers who automatically get access to each new document
MetadataMetadata copied to every document, for example linked to dynamic fields
Notifications and tasksReminders and tasks every new document inherits

Save your changes

Template edits must be saved explicitly; they are not autosaved. Save regularly during longer sessions. If you try to leave with unsaved changes, a browser prompt warns you. Cancel leaving, save, then navigate away. If you are logged out before saving, unsaved changes are lost.

Publish

Check the template in the preview, then click Publish. It's now available to everyone in the selected teams when they create a document.

If fynk warns about Unplaced signature or voting blocks, you can place the blocks in the content first or choose Publish anyway. This warning does not prevent publication.

If publishing doesn't work, see A template can't be published.

Good to know

  • Start with a simple template, such as an NDA, before building complex ones with many conditions.

  • Editing a published template does not unpublish it. Once you save, documents created afterwards use the updated template. Existing documents stay as they are. Unpublishing is a separate, manual action.

  • Notifications target document users, including users added through auto-access. Team assignment alone does not subscribe everyone in that team. Teams can be added as notification recipients on individual documents, but cannot be preset as recipients globally or in the template.

  • Documents created from a template keep a link to it, which you can see in the document list.