Participant
Overview
The Limited Document Visibility (LDV) settings allow an agreement to contain multiple files that are selectively visible to the recipients depending on which settings are enabled and how the agreement is configured.
Example use cases include:
- Sales agreements that require internal oversight or approval before being sent to the customer.
- New hire documentation to be delivered after the offer letter is accepted.
- HR documents that require internal processing outside the initial signer's scope.
Here's a quick video that captures the high-level use:
Availability:
Limited document visibility is available for the enterprise license plan only.
Configuration scope:
LDV can be enabled at the account and group levels.
How document visibility works
LDV rules can be enabled at the account and group level.
LDV rules only expose the file content explicitly assigned to any given recipient.
File content is assigned to a recipient by adding at least one field assigned to that recipient.
- LDV is file-based, not page-based. If a file has 40 pages, and the recipient has one field assigned to them on one page, the recipient can see all 40 pages of the file.
- If the file contains no fields for the recipient, the entire file is excluded from that recipient's view.
- If there are four files, and the recipient needs to see all four, then at least one field must be applied to one of the pages of each file.
- If page-level control is required, the file must be divided into individual files, each containing one page.
In the example to the right, there are two signers and two documents in an agreement.
Signer 1 sees both documents, as there is a field assigned on both docs (Field 1 and Field 2)
Signer 2 will only see Doc 2 because they don't have an assigned field on Doc 1.
- Doc 2 is visible because Field 3 is assigned to Signer 2.
LDV rules expect two prerequisites:
- There must be more than one recipient
- Recipients include any user added to the signature/approval process
- CC'd parties are not recipients.
- There must be more than one file added to the agreement
- Files are any attachments used to build the agreement (.doc, .xls, .pdf, PNG, etc.)
If either of the above requirements isn't true, LDV rules are suspended for that agreement.
Signers will only see files containing signature, initials or data entry fields assigned to them is the root control that enables the LDV experience and the set of subordinate controls. If this control is disabled, LDV as a whole is disabled in the recipient experience.
All recipients and CC'd parties see all files all the time.
|
During the signing process |
When the agreement is completed |
---|---|---|
Sender |
All documents |
All documents |
Internal Recipient |
All documents |
All documents |
External Recipient |
All documents |
All documents |
Internal CC |
All documents |
All documents |
External CC |
All documents |
All documents |
External Archive Recipient |
NA |
All documents |
After enabling the root LDV control, there are three additional configurations to control visibility depending on your preferred experience:
Using LDV with the REST API v6
The sender can use the REST API v6 to explicitly grant visibility to documents.
REST API v6 calls ignore all document visibility settings in the UI, as the API call overrides account/group level settings.
The only carry-over behavior is that the sender must specify a document label if it specifies a form field for a particular recipient.