Send generated documents automatically for Signing.
To start with a HelloSign delivery, choose the
Hello Signoption from the list of deliveries available in the
Configure New Deliveryview.
To enable Text Tags and make sure you enable Use Text Tags. Your Text Tags will be converted into UI components for the user to interact with. Keep in mind that by default the tags themselves will remain on the page. To hide the tags from the end user you can change the text color to match the background (such as white on white). Alternatively you can set Hide Text Tags although we don't recommend this because auto-removal can lead to unwanted clipping.
To begin and end a tag, use square brackets [ ] in your document. Within the square brackets, use the pipe character | to divide the parts of the tag. The first part of the tag is the type. The second part indicates if it is required or not. The third part indicates which signer in the list of signers needs to complete the field. The last two parts are optional and are for setting a label and unique ID.
For example: [text|noreq|signer1|Label|UniqueId]
HelloSign Text Tags
Text Tags let you specify which signer the field is for, what type of field it is, and if the field is required or not in addition to the relative size of the field. The types of fields available are the same as when you create a template:
The only valid values for field requirement are "req" and "noreq". The value defaults to "req" if the entry is not understood.
When you write a Text Tag you must assign it to somebody. The number N in "signerN" represents the signer index, For example with these two text tags:
You have specified that signer is required to sign and signer is required to initial.
Enabling optional recipients in the HelloSign delivery will skip invalid signers and carbon copy (cc) entries.