Skip to content

Use a template

A template is a document you have already prepared once — its fields and its signer positions are saved, so sending the same kind of document again means filling in a short form rather than repeating the whole wizard.

Click the template in the Templates list: Template details opens, with Use template at the top. The Use template dialog has the template’s name in its title and, underneath, how many signers it asks for — for example “This template has 4 signers: 3 required and 1 optional.” You are asked for two things.

Fields — the values that vary between documents. Each field shows a readable name and, underneath, the DOCX marker ({{FieldName}}). Required ones carry an asterisk; the rest are folded under Optional, with their number in brackets — open it if you want to fill them in.

Signers — for each signer the template expects, a row with the number, the template’s signature types (for example Rubrica · CMD) and Name, Email and Phone. The Choose from contacts icon fills the row from your contact list, and Import list — “One person per line: Name, email” — fills several at once, in the template’s order. A green tick marks each complete signer, and the counter tells you how many required ones are left: “2 of 3 required filled in”.

Optional signers sit apart, under Optional, each with an Include switch. With it off, the row cannot be filled in and the signer is left out of the document.

On a wide screen, Fields and Signers sit side by side, and each column scrolls on its own: a template with many fields does not push the signers off the screen. On narrower screens they stack, one under the other. On a phone, the dialog takes the whole screen and splits into two steps, 1 · Fields and 2 · Signers, with Next between them.

Send stays disabled while anything is missing, and beside it you see what: “«Landlord Name» is missing” or “Signer 2 is missing”. A mistyped email is marked “Invalid email”.

If the template has fields for the signer to fill in, you do not answer them here: each signer answers them, on the document, when signing. See Fields the signer fills in when signing.

Then select Send. On success you get “Document created and sent for signature.”, and the application takes you to the document list, with the panel of the document just created open.

The Use template dialog: the template fields and the signers, with
Send.

On a free organisation that has not confirmed its mobile number yet, Send first opens One more step before sending; once the number is confirmed, the document is created and sent with the values you already typed. See Confirm your mobile number.

If your balance is short, the server refuses the send and the same purchase dialog as the wizard’s opens — see If your balance is short.

Templates can carry more than flat text fields. When the template uses repeats, conditions or images, the Fields column ends with Advanced data (JSON), already filled with a skeleton. It accepts a JSON object for the cases a plain field cannot express:

Arrays for repeats, true/false for conditions and images (base64/URL).

So a list drives a repeated block, a boolean shows or hides a section, and an image can be supplied inline or by URL. Malformed input is rejected with “The data JSON is invalid.”

Template details shows what a template contains before you commit to using it:

General Name, Description, Status
Created by, Created on, Last modified on
Automatic fields The fields it will ask you to fill, and which are Required
Signers The signers it expects, whether each is Required or Optional, the signature types and the page of each marker
Template ID (API) At the top, by the name, with Copy — the identifier used to drive this template from the API

Download template downloads the underlying file.

The Template ID (API) is worth knowing about even if you never write code: it is how an integration refers to this exact template.