Now that you've seen what electronic signatures can do, let's look at how to set them up. Your first step in gathering electronic signatures will be to create a Document Template by navigating to Admin Tools > Settings > Signature Documents. The template will be used to generate the individual documents a person will sign. Out of the box, Rock ships with an example Photo Release template and a Field Trip Release template. You can use these templates as a reference for creating your own. NoteSignature Input TypeAs described below, we very strongly recommend using a Typed signature and not a Drawn signature. Both are equally valid in terms of legal representation, however a drawn signature is considered Personally Identifiable Information (PII) and storing it in Rock may have additional legal consequences. Name - Be sure the name of the document is clear and concise. This name will appear elsewhere in Rock when you need to select a template to use. The name is also included in theElectronic Signature ReceiptSystem Communication.Description - A good description can help avoid problems or confusion in the future. In this example it's made clear in the description that the template needs to be provided with theSignedByPersonand theAppliesToPerson.Document Term - Out of the box theDocument Termis used by theElectronic Signature ReceiptSystem Communication. TheDocument Termappears after the name of the Signature Document in the communication. You'll also see it in other places, like during event registration when the person is asked to "Please Sign the [Document Term] for [Person]".Signature Input Type - Here you can select whether the signature should beTyped(the person types their name) orDrawn(the person uses a mouse or finger to draw a signature). Because a drawn signature is considered Personally Identifiable Information, we strongly recommend usingTyped.File Type - The signed document will be stored in Rock, and this setting determines which type of file it will be stored as. In most cases this will probably be set toDigitally Signed Documents, but you can use other file types if needed.Completion Email Template - This is where you'll select which System Communication should be used to send a copy of the signed document to the person who signed it (technically theSignedByPerson). TheElectronic Signature Receiptthat ships with Rock was created for this purpose.Valid in Future - Determines whether documents of this type should remain valid for meeting future eligibility requirements. For example, a signed waiver might be reused for subsequent events without needing to be re-signed, as long as it is still valid under your organization's policies.Template Tips - Click here to display helpful tips for creating your own template. The attribute keys in the template must match the attribute keys configured in your workflow or event registration.Lava Template - The template provided here becomes the body of the document the person is asked to sign. This is where you'll design your document content. Lava merge fields can be used to pull in dynamic information, such as workflow attributes, making the document adaptable for different use cases. This template is designed to be used with theElectronic Signatureworkflow action type. NoteUsing Multiple SignaturesBy default, the template places a signature at the bottom of your PDF. To change its location, or add a signature in multiple different spots in your document, use <!-- [[ SignatureDetails ]] -->. Each instance of this keyword will be replaced with the signature instead of a single signature appearing at the bottom. The legacy method of setting up a Signature Document (using a third-party provider like SignNow) can still be accessed from the page above. Simply edit the block settings and set Show Legacy Signature Providers to "Yes". Keep in mind that support for these signature providers is ending, so you need to transition your documents now if you haven't already. For instance, the Registration Entry block (Obsidian) does not work with the legacy documents.