Nintex Sign powered by Adobe Sign

The name or email address of the person sending the request. The initiator is displayed as the 'From' address to the recipient.

External email addresses can be used.

The first time a workflow is run after being published, the initiator must authorize Nintex to access the Adobe platform.

Note: Authorizing Nintex Workflow only authorized a single workflow.

Steps in the authorization process

Once the action is executed, a message will be sent to the email address specified in the initiator field. The message will contain the following information:

• Subject: Nintex: Request authorization to access Nintex Sign.
• Contents: Contains links to authorize the operation.

When the initiator user clicks the link to authorize the operation, the authorizing user will be prompted to do the following:

• Log in to Adobe Sign at https://secure.echosign.com/public/login.
• A success message will be displayed if your login was successful.

The sequence the recipients sign the document.

• Complete in order: Recipients receive the document to sign in the order listed by the initiator. Nintex Sign sends each recipient the documents to sign only after the previous recipient completes signing.
• Complete in any order: Recipients can sign the document in any order. Nintex Sign sends the document to all recipients at the same time to be signed in any order.

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 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 an 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.

Name of the document being sent to the recipient.

To insert a reference, select the icon.

The message Nintex Sign includes with documents being sent to the recipient. Only recipients can see the message.

To insert a reference, select the icon.

The number of days a document will be available to sign by the recipient.

Use the drop down list to set specific limitations.

The number of times the recipient is reminded to sign the document.

The frequency options are listed below:

• None: No reminder emails will be sent to the recipient.
• Once: One reminder email will be sent to the recipient.
• Daily until signed: A daily reminder email will be sent to the recipient.
• Weekly until signed: A weekly reminder email will be sent to the recipient.
• Week-daily until signed: A daily reminder email will be sent to the recipient every week.
• Every other day until signed: A reminder email will be sent to the recipient every other day.
• Every third day until signed: A reminder email will be sent to the recipient every third day.
• Every fifth day until signed: A reminder email will be sent to the recipient every fifth day.

Enter the URL where the recipient will be redirected to after they sign the document.

Note: The URL should be specified in full with http/https.Example: https://www.nintex.com.

Create a password for the recipient to enter to unlock the document before signing. The set password will be used to access the document after signing.

For more information, see Lookups reference

To insert a reference, select the icon.

Select one of the two options for the document location:

• SharePoint
• Nintex Sign

The document will be sent to the recipient.

The name of the template will vary depending on which document location is selected.

• If SharePoint is selected, the name of the template will be displayed as SharePoint relative URL.
  • The SharePoint relative URL can be a full URL.
• If Nintex Sign is selected, the name of the template will be displayed as the name of the template in Nintex Sign.

To insert a reference, select the icon.

Click Add Document to add multiple documents.

Note: If there are multiple documents, they will be merged into one single agreement.

The maximum number of documents is 50.

The maximum combined file size is 10 MB.

Select one of the following options:

• Document library
• Enter a URL
• Attach to current item
  • This option is only available for List workflows.

Click Select a document library or folder to choose a file location.

The output location is where the document will be stored after signing.

The variable where the Nintex Sign agreement outcome for the signed documents can be stored.

Possible outcomes:

• Signed: The agreement was signed by all recipients.
• Unsigned: The agreement was not completed, or a recipient did not sign.
• Error: Workflow was suspended.