Require an NDA Before Sharing Documents
Set up an NDA access step and check the recipient flow, document version, and signed record.
On this page (7 sections)▼
An NDA gate should answer a practical question: has this recipient accepted the intended agreement before seeing this material? Adding a checkbox without checking its wording, scope and record leaves that question unresolved.
Start with approved terms and a harmless sample document. The workflow below is a recommended verification process, not a report of a completed product test. A click-through access step and a certificate-based digital signature are different mechanisms.
1. Decide what the agreement covers
Ask the person responsible for the agreement to confirm the parties, purpose, permitted recipients and material covered. Use their approved version rather than copying unrelated terms from another transaction. The right wording depends on the arrangement; the sharing tool does not decide it for you.
Choose whether acceptance belongs to one document link, a folder or the whole room. Write that scope in your release notes. An agreement on one access path should not be assumed to cover every other path.
| Question | Record before configuration |
|---|---|
| Which agreement? | Approved text and version reference |
| Who accepts? | Intended recipient or authorized representative |
| What is covered? | File, collection or transaction scope |
| Where is the record kept? | Responsible owner and approved storage location |
2. Configure the access step
In SendNow, open the document link settings, enable the NDA agreement gate and enter the approved text. The documented recipient flow records click-through acceptance with a name, email and timestamp; it is not a qualified e-signature. SendNow: NDA agreement gate
Preview the actual text after saving. Look for missing paragraphs, accidental placeholders and unreadable formatting. Confirm that any linked reference can be opened before confidential content is disclosed.
If access must be limited to invited people, configure recipient authorization separately. Acceptance alone does not establish that someone was allowed to receive the file. Treat recipient identity, contractual acceptance and document permissions as separate checks.
3. Test both acceptance and refusal
Create a sample link containing no confidential information. Open it in a fresh browser session using an appropriate test identity. Do not use the owner's authenticated session as the only test.
- Confirm the agreement appears before the content.
- Check that the text can be read on a phone.
- Leave the agreement unaccepted and attempt to continue.
- Accept using the test identity and verify the permitted content opens.
- Check that the resulting record refers to the intended agreement and link.
Also test another entry point if the file appears in a collection. Record observed outcomes rather than assuming that individual-file and room settings are interchangeable.
4. Preserve the release context
Keep the approved agreement version, file version and acceptance record together in your internal release register. An analytics row without agreement context may be difficult to interpret later. Preserve available records according to your organization's retention process; do not assume a dashboard retains them indefinitely.
Before replacing a shared document, check the provider's replacement restrictions and whether renewed acceptance is needed for the changed material. Keep the previous release privately. Do not silently overwrite a signed or accepted record to make the history look simpler. SendNow: Replace a shared file
5. Explain the next step to recipients
Send a short instruction stating who the document is for, that an agreement appears first, and whom to contact if they cannot proceed. Avoid claiming that the gate makes disclosure impossible. Someone who legitimately views content can still remember or otherwise reproduce it.
A useful completion record names the agreement, release version, test identity and observed result. If the agreement fails to appear or the acceptance record is missing, pause that sharing path until the issue is understood.
Frequently asked questions
Does the NDA apply to the whole data room?
Only when the configured workflow and approved agreement actually establish that scope. Verify room, folder and direct-link paths individually instead of inferring inheritance.
Can I replace the file after acceptance?
Check the product restrictions and the agreement owner’s instructions first. A new version may change the disclosure or require a new acceptance process; retain the previous release record.
Is a checked box a digital signature?
A click-through acceptance record is different from a certificate-based PDF signature. Use the mechanism approved for your transaction rather than treating their labels as equivalent.
Before you share
Release the link when the correct text appears before access, the intended recipient can complete the flow, and the acceptance record can be interpreted alongside the document version.
Related articles
Sources and editorial disclosure
Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.
VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.
Related Guides & Research
Recommended next reading for deal teams and transaction leaders.
Restrict a Document to Specific Emails
Limit access to intended recipients and distinguish an allowlist from simply asking viewers to type an email.
How to Create a Document Microsite
Build an organized document page with clear file labels, navigation, and a useful next step.
Are Your Document Views Real?
Investigate automated opens and repeated sessions before using view counts for follow-up.