Working with signers
A signer is a person who is required to complete one or more fields in a signing request. A signer is identified by their name and email address, and you assign the fields they are responsible for completing.
Signers do not need an Undersign account. They can open the secure signing link they receive and complete the signing request directly in their browser.
Adding a signer
When preparing a signing request or template, add each person who needs to participate by providing their name and email address.
You then assign that signer the fields they need to complete, such as:
- Signature
- Initials
- Date
- Text
- Checkbox
For requests with multiple signers, each signer can have their own set of fields. You can also control whether a signer can see fields or information entered by other signers using Field Visibility.
How signers work in a request
A signing request can have one or multiple signers. When there are multiple signers, you can control when they sign and what information they can see.
Signing order
Parallel signing
All signers can access the request at the same time and complete their assigned fields independently.
Sequential signing
Signers complete the request in a defined order. For example, Signer 1 completes their fields first, followed by Signer 2.
See Sequential Signing.
Field visibility
Field visibility determines what each signer can see when completing the request.
For example, in a request with two signers:
- Signer 1 can be allowed to see or not see fields completed by Signer 2.
- Signer 2 can be allowed to see or not see fields completed by Signer 1.
This lets you keep certain information visible only to the signer it belongs to, when required.
See Field Visibility.
Signer identity
The signer's email address identifies them within the signing request. The signing invitation and other request notifications are sent to this address, and the signer's activity is recorded against it in the Audit Trail.
The signer does not need to create an Undersign account to sign.
Signer roles in templates
When a template is designed for a recurring workflow, you can define signer roles instead of specific people.
For example, a template might have the roles Primary Signer and Co-signer. When the template is used for a new signing request, you assign actual people to those roles.
This allows the same template to be reused for different recipients without changing its field assignments.
Reuse signers
If you frequently send requests to the same people, you can save their details in Contacts and select them when creating a signing request instead of entering their information each time.