|By Mat Rider||
|July 29, 2014 07:00 AM EDT||
Every DocuSign envelope uses email authentication for security. If you require an extra level of security on your documents, you can add additional authentication methods.
In addition to the standard email authentication, DocuSign provides three authentication methods and allows you to select one or two additional authentication options for each envelope recipient. You can use different authentication options for each recipient.
When using the Access Code Authentication option, signers must enter an access code you've created prior to viewing the document.This is a common form of additional authentication.
For more information on other Signer Authentication options, please review Signer Authentication Options.
To add an access code to an envelope as a sender, follow these steps:
- Create a new envelope.
- Add documents to the envelope normally.
- Add a recipient normally.
- Click on the Identify drop-down to select the authentication option you want to use for the recipient.
- Click to enable the Access Code field, then enter the desired access code (access codes can include upper case or lower case letters, numbers, and special characters).
Note: You must provide this access code to your recipient. It is recommended that you provide the code over the phone or using some other secure method. There is no additional fee for using this authentication check. The maximum length of an Access Code is 50 characters.
- Add any other recipients for the envelope.
Note: You are not required to set any security options for the other recipients.
- Add the Email Subject and any Email messages, select any Envelope Settings, add tags to the documents, and complete sending your envelope normally.
The envelope is sent and any recipient with an active security option must complete the authentication before they can access the envelope.
To view an envelope that requires an access code as a signer, follow these steps:
- Open the DocuSign notification email from the sender and click View Documents.
- Enter the code provided to you by the sender, then click Validate.
Note: You have three attempts to enter the code. If you fail to enter the correct code on the third attempt, the sender will be notified and must resend the document. If you have not received the code or lost it, click I never received an access code to prompt the sender to resend it.
We certainly live in interesting technological times. And no more interesting than the current competing IoT standards for connectivity. Various standards bodies, approaches, and ecosystems are vying for mindshare and positioning for a competitive edge. It is clear that when the dust settles, we will have new protocols, evolved protocols, that will change the way we interact with devices and infrastructure. We will also have evolved web protocols, like HTTP/2, that will be changing the very core...
May. 30, 2015 03:30 AM EDT Reads: 5,395
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happe...
May. 30, 2015 03:00 AM EDT Reads: 5,805
May. 30, 2015 02:00 AM EDT Reads: 6,190
May. 30, 2015 01:00 AM EDT Reads: 2,013
May. 30, 2015 12:00 AM EDT Reads: 4,259
May. 29, 2015 11:45 PM EDT Reads: 1,500
May. 29, 2015 11:15 PM EDT Reads: 1,025
May. 29, 2015 09:00 PM EDT Reads: 4,994
May. 29, 2015 04:27 PM EDT Reads: 529
May. 29, 2015 04:00 PM EDT Reads: 5,322
May. 29, 2015 04:00 PM EDT Reads: 3,369
May. 29, 2015 03:45 PM EDT Reads: 874
May. 29, 2015 03:45 PM EDT Reads: 4,813
May. 29, 2015 03:21 PM EDT Reads: 569
May. 29, 2015 03:00 PM EDT Reads: 4,946