Thereforeâ„¢ Help

E-mail

Yes

E mail address of the signatory

john.doe@nomail.com

First Name

No

First name of the signatory

John

Last Name

No

Last name of the signatory

Doe

Role

Yes

Role of the signatory

Signer

Message

No

Private message for the signatory

Please sign this document

Authentication

No

Authentication method for the signatory

Password

Password

Yes/No

Only mandatory when Authentication set to Password

12345

Country Code

Yes/No

Only mandatory when Authentication set to Phone

+43

Country ISO Code

Yes/No

Only mandatory when Authentication set to Phone

AT

Phone

Yes/No

Only mandatory when Authentication set to Phone

067123456

Signer

Signers are required to apply at least one signature to an agreement. This role is the default recipient role. Each signer on a transaction needs to have at least one required signature field assigned to them. If the system does not find a signature field for the signer, it automatically generates a signature block at the end of the document.

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. The approver role works well for situations where someone needs to "okay" a document before it's sent off to the signer.

Acceptor

Acceptors are mechanically the same as Approvers in that they do not need to apply a signature, but if form fields are assigned to them, they will be available as you would expect.

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.

•Delegating will transfer the Certified Recipient role to the nominated delegatee

•Declining will terminate the Agreement

•Acknowledging the Agreement continues the signature cycle

Form Filler

Designed specifically for customers that have a need to fill in form content during the signature process, but don't have the systems in place to programmatically build custom documents or push field content from a database to the form.

Form Fillers can be designated within a signature cycle, but are not required to apply a signature of any kind. All field 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.

This role does not replace the ad-hoc option for a signer/approver to delegate their participation. Rather this role is used when a human check point/routing option is needed in a workflow that has to initiate Agreements without knowing the full recipient list beforehand. 

Email

Signers will receive an email with a link to review and sign your document. An email notification is also sent for the other identity verification options: password, KBA, or social.

Password

Require signers to enter a password you specify.

Phone

Signers will be required to enter a verification code that is sent to their phone via SMS or voice call.

Knowledge Based Authentication (KBA)

Require signers to provide their name, address and optionally last 4 digits of their SSN and then answer questions to help verify their identity. Available only in the US.

Adobe Sign

Require signers to verify their identity by signing into Adobe Sign.

Government ID

Government ID is a form of identity verification that requires signers to scan their Government ID images via their mobile phone camera and get them verified. An identity report will be available through the Manage page.

Sender

No

The email of API sender using the account or group token. If it is not specified, then the caller is inferred from the token.

Reminder Frequency

No

Optional parameter that sets how often you want to send reminders to the participants. If it is not specified, the default frequency set for the account will be used.

Language

No

The locale associated with this agreement - specifies the language for the signing page and emails. If none specified, defaults to the language configured for the agreement sender

Password to secure the PDF

No

The secondary password that will be used to secure the PDF document. Note that Adobe Sign will never show this password to anyone, so you will need to separately communicate it to any relevant parties

Signing deadline (days)

No

Time after which Agreement expires and needs to be signed before it.

Note:   The integration key can be retrieved from the Adobe Sign portal