One-Click NDA

Available on:  Advanced , Enterprise 

• Setting up an NDA
• Updating the NDA on File
• Using the NDA link setting
• Reviewing NDAs in-app
• Viewer Experience
• NDA Certificate
• Trialing NDAs
• Downgrading from Advanced
• DocSend NDA FAQ

Non-Disclosure Agreements in DocSend
With One-Click NDA, users can upload a signable document and present it as a downloadable, non-disclosure agreement for each visitor to review before gaining access to a document or Space. One-Click NDA is designed to provide a simplified and faster process for sharing and executing an NDA. This article will detail how to create and share DocSend links utilizing One-Click NDA, how viewers will review and sign the NDA, and a FAQ section. 

Legal: Signers are legally required to agree to the electronic records and signature and DocSend’s terms of service and to the document owner’s Non-Disclosure Agreement terms. 

Setting up an NDA
Admin users can upload and manage an NDA in the company NDA settings. NDA’s cannot be moved to personal folders and must be available to admins. Additionally, only admins are able to delete the NDA. Here is a brief overview on how to set up an NDA:

Upload an NDA document - Under the Company Settings page, admins can upload a document that will act as the NDA for the account. The document can be directly uploaded through the NDA settings with the option of choosing which folder from the Content tab the file will be hosted at. *Please note, the NDA document must be available in the Team Folder section of the Content tab.

Alternatively, account admins may select an existing file within the account to act as the NDA by choosing the option to "Select from content". For more information on how to include an existing file in the account as an NDA, please follow the steps listed below:

1. Upload an NDA document - Under the Content tab, admins can upload a document that will act as the NDA. The document will need to be uploaded and shared in a team folder and visible to others in the team (see Uploading documents and Organizing content with folders).
   
   
2. Enable eSign - After uploading the document, users will need to convert the document into a signable one before being able to use it as the NDA for the company (see Signable documents).
   
   
3. Updating NDA settings - Once converted, admin users can select any shared signable document as the company NDA in the NDA settings. Note: the NDA document must be available in a team folder and also converted to a signable document.

Updating the NDA on File

If changes need to be made to the NDA on file, an admin user can do so via their NDA Settings page. Selecting "change" will prompt users to select a new NDA shared within a team folder. Alternatively, by "removing" the current NDA admins may then choose to upload a new NDA from their desktop or device. 

Using the NDA link setting
Once enabled, users will have the option to configure an NDA on links and Spaces. Enabling the NDA link setting will also automatically enable the link setting to provide a name and email address as apart of the NDA process. Here’s a brief overview on how to use the NDA link setting:

1. Choose the link settings - During link or Space creation, users can expand the advanced link setting to choose the ‘Require NDA to view’ link option.

• Finish creating the link or Space - Press ‘Create Link or Space.
  
  
• Update Settings real time - Links or Spaces with the NDA feature can be updated to add or remove the NDA settings.
  
  
  • In documents:
    
  • In Spaces:
    

Gmail/Chrome and Outlook Extensions
Users can also configure an NDA while using the Gmail or Outlook extension. For more  details on using the extensions, see our help center articles on Creating Links with the Gmail extension and Creating Links with the Outlook add-in.

• In Gmail/Chrome
  
  
• In Outlook  
  

When an NDA is not Configured  
If an NDA is not selected, the NDA link setting will not be available to use until one is added. A warning message will appear for all users when an NDA is not selected.

• For members, a note will be added that the NDA is not yet set up and to contact their admin to upload or select an active NDA
• For admins, a message will be available linking to the NDA settings to upload or select an active NDA. 

Reviewing NDAs In-app
Internally, users will be able to see which contacts have signed an NDA under the document that is being shared. All NDA activity will be visible in the contact rows of the document, the document details page, and the accounts and contacts page. Users will also receive desktop visit notifications when a  visitor views and signs an NDA for a document. Users will be able to download the signed NDAs from any of the options listed above.

Important: Signatures to the NDA will be in the document that is shared under the document details under recent activity, and not the NDA document itself.

Contacts who have signed previous versions of the NDA will be shown with a gray NDA tag. Active NDAs will be shown with a green tag. Admins can update the NDA anytime by accessing the NDA settings.  

Active Signed NDA:

Previously-active Signed NDA:

Viewer experience
As a part of the NDA process, visitors who download the NDA document and agree to the terms are providing a signature before gaining access to the document. Visitors will need to provide the following details before gaining access to the NDA-enabled document: 

• Provide their name 
• Provide their email address
• Download the NDA
• Agree to the electronic records and signature and DocSend’s Terms of Service
• Agree to the Non-Disclosure Agreement terms

DocSend Certificate 
Similar to DocSend’s eSignature, a certificate will be emailed to the sender and signer along with a signed copy of the document after the signature has been executed. This will include information about the document and the signer and an audit trail of all the events that happened as part of the NDA signing. 

The signer and sender will receive an email notification with a zip file containing both the signed copy and document certificate detailed with an audit trail of all the events leading to the signature. 

Signer:                                      Sender:  

Signed NDA copy

Certificate Document Details

• Document name
• Document ID: A unique id for the signed document and matching certificate
• Page count: Number of pages in the document
• Pages signed: Number of pages the signer signed
• Original checksum: A hash of the original document’s location
• Final checksum: A hash of the signed document’s location
• Signature: An image of the signer’s signature

Audit Events
Similar to eSignature, all events will include a UTC timestamp for when the event occurred. Additional information may be included in each event, such as location, IP address, user agent, etc. Events that may be included:

1. Visitor information entered: Once the visitor has entered their information in the email/name prompt.
   • Includes: Visitor name, visitor email, IP address, location, user agent, whether the name/email was updated
     
2. Visitor authorization: Once the visitor has been authorized to view the document (i.e. has entered the correct password, is on the allowed viewer list, has verified their email address)
   • Includes: Authorizations passed, Visitor name, visitor email, IP address, location, user agent. If a link or Space requires NDA to view, “NDA downloaded” will be added as an additional authorization method to the list of authorizations passed
     
3. Email Authentication email sent
• Includes: Email
  
4. Email verified: When the visitor returns to DocSend with a valid email authentication link
   
   • Includes: IP address, location, user agent
5. Document signed
   • Includes: Visitor name, visitor email, IP address, location, user agent
     
6. Document completed: DocSend generated the signed PDF
   
   Important: There are two additional events that are unique to the NDA signature and will always be included in the audit trail of every signed NDA document:
   
   
7. Document downloaded: When the visitor clicks the “Download Non-Disclosure Agreement” button, or clicks the link to “Non-Disclosure Agreement” in the checkbox text
   • Includes: IP address, location, user agent
8. Terms agreed: When the visitor checks the checkboxes for agreeing to use electronic records, signatures, DocSend’s Terms of Service, and the terms of the NDA
   • Includes: Visitor name, visitor email, IP address, location, user agent

Note: There can be multiple of all events except for the signed and completed events. Events will be merged by email address and document, so if the signer is using the same email address on multiple devices for the same active NDA document, those events will be grouped together in one audit trail.

Trialing NDA
Users trialing the Advanced plan will be able to capture up to 20 signatures. Once a user hits 15 signed NDA documents, an automated email will be sent informing the user that they will need to add a card in order to get more NDA signatures. Once the user hits 20 signatures, the feature will be removed from their account.

Downgrading from Advanced or Enterprise
When downgrading to the personal plan or limited trial, all links and Spaces utilizing premium features such as the NDA link setting will be deactivated upon downgrading. Admins on the account can remove the NDA centrally in the NDA settings prior to downgrading, however, all links and Spaces utilizing the NDA link option will still be deactivated. Users can remove the NDA option to re-enable the link or Space. Here's how:

1. Go to the link and select the Link settings options menu
2. Press Update link and the link will be accessible again
3. Uncheck the premium setting option, e.g allowed viewer, email authentication, NDA

DocSend NDA FAQ

• Can I have multiple NDAs for my company?
  • User accounts can only have one NDA applied at a time, but can update their NDA to a new version at any time and all links will updated automatically.
• Where will the NDA signatures be to review?
  • NDA signatures will be visible in the document page details of the content that is shared with visitors, and not the NDA upload itself.
    
    
• Can you map Salesforce data SFDC data for NDA?
  • Users cannot currently map NDA data from DocSend into Salesforce
    
    
• Can a contact sign an NDA and have it represent the whole company/account?
  • One-click NDA is at the contact level, not the account/company level, so by signing an NDA, an individual is only signing on behalf of themselves and not the company.
    
    
• Is one-click NDA applicable outside of the U.S.?
  • At this time, DocSend is compliant with UETA and ESIGN regulations which are specific to the US only. Please seek additional legal advice if One-click NDA would work for your organization.
    
    
• Can there be multiple signatures on an NDA?
  • Similar to eSignature, one-click NDA only supports one signature at this time.  
    
    
• What happens when an NDA is disabled or removed?
  • If the active NDA document was removed, all links that currently require NDA will still have the NDA required option checked, but upon visiting those links, the visiting flow will be as if the NDA required option was not checked (the links will continue to require email and name when viewing)

• Is the NDA searchable?
  • The active NDA document will be marked with an ACTIVE NDA tag in document rows and on the document details page.
    

• Does NDA signing work on mobile?

  • Yes, NDA’s can be created and signed on most mobile devices.
    
    

For more enhanced security features, please check out related articles on:

• Allowed Viewers
• Watermarking
• Email Authentication