|
Recipient* |
The primary user who will receive the document to sign. Enter the email address of the person you want to send the document to. The recipient does not need an Adobe ID or account.
The recipient can also enter:
- Variables: Variables can be populated with a dynamic list of email addresses.
- Example: You can query a list to get a list of email addresses and then use the collection for the recipient field. Nintex Sign will go through all the email addresses in the variable and use the same settings for role and identity for each email address as if they were manually added.
- Workflow constants: Workflow constants can contain multiple email addresses and Adobe will send the agreement to all the emails ids.
Select the address book icon and open the Select People and Groups window to find people from your organization.
Recipient role*
There are different recipient role types depending on your workflow requirements as follows:
Field
|
Description |
Signer |
This role is the default recipient role. Signers are required to apply at least one signature to an agreement.
|
Approver |
Approvers are not required to sign or interact with any fields. All approvers need to do is enter their name before sending the transaction to the signers. Fields can be assigned to approvers, and if those fields are required, they need to fill them out. |
Acceptor |
The Acceptor role is appropriate when the recipient needs to acknowledge acceptance of the agreement without formally approving the content. |
Certified Recipient |
Certified Recipients can have no (zero) form fields assigned to them. During their "signature" process, they will be asked to either delegate, decline or acknowledge the agreement.
|
Form Filler |
Form Fillers can be designated within a signature cycle, but are not required to apply a signature of any kind. All fields types can be assigned to a Form Filler, including signature fields if desired. |
Delegator |
The delegator role is designed for workflows that require a person to make the final judgment on who the correct next person is that should sign or approve the document. If the delegator role is selected, a new dropdown will be displayed to select who to delegate the agreement to.
|
For more information, see Allow various recipient roles. |
Identity authentication*
When obtaining signatures or approvals from recipients, many agreements demand a higher assurance of authentication than simple email verification. Adobe Sign provides several options for senders to insert a second-factor authentication into the process, establishing a higher confidence level that your recipients are properly certified.
Field |
Description |
Email |
No authentication required. The recipient will receive an email with a link to sign the document.
|
Password |
An alphanumeric password is set by the sender while configuring the agreement that the signer must enter. |
Social |
The signer is required to authenticate to one of the allowed third-party services: Google, Linkedin, Twitter, Facebook, Yahoo, or Microsoft Live. |
Knowledge based
|
The signer is required to provide their name, address, and optionally the last 4 digits of their SSN, then answer questions to verify their identity. Powered by RSA. Available only in the US. |
Phone (SMS) |
Signers will be required to enter a verification code that is sent to their phone via SMS or voice call. |
Adobe Sign |
The signer is required to authenticate Adobe Sign. |
Government ID |
The recipient must provide an acceptable government-issued ID and selfie.
|
Click Add Recipient to add multiple recipients. The maximum number of recipients is 50. For more information, see Use identity authentication methods. |
|