Managing Document Visibility

By default, during a Signing Ceremony all recipients can view all documents in a transaction.

The Document Visibility feature provides greater flexibility by enabling integrators to control which recipients can view specific documents in a transaction during a Signing Ceremony.

This can save recipients from having to process documents they don’t need to see, and it can ensure that documents with sensitive information are viewed only by their intended recipients.

The Document Visibility feature is disabled by default. It must be enabled for your account before you will be able to use it. For more on this, contact Technical Support (sign.support@onespan.com; 1-855-MYESIGN).

The following sections illustrate various aspects of the Document Visibility feature:

NOTE:
  • If a recipient has a signature on a document, that document cannot be hidden from the recipient.
  • If there is a signature on a document for a recipient, the Electronic Disclosures and Signatures Consent page cannot be hidden.
  • Documents cannot be hidden for group recipients or for notary recipients.

Specifying the Recipients Who Can View a Document

The code samples in this section involve three signers and three documents. The samples specify which signers can view each document.

Specifically, the samples specify that:

  • The first document can be viewed only by the first and third signers.

  • The second document can be viewed only by the second and third signers.

  • The third document can be viewed only by the second and third signers.

Getting a List of the Recipients Who Can View a Document

The code samples in this section involve three documents and a number of signers. The signers who can view a given document are listed in an associated package, which is identified by its “packageID”. The samples get that list of signers for each document.

Specifying the Documents a Recipient Can View

The code samples in this section involve three signers and three documents. The samples specify which documents can be viewed by each signer.

Specifically, the samples specify that:

  • The first signer can view only the first document.

  • The second signer can view only the second and third documents.

  • The third signer can view all three documents.

Getting a List of the Documents a Recipient Can View

The code samples in this section involve three signers and a number of documents. The documents that a given signer can view are listed in an associated package, which is identified by its “packageID”. The samples get that list of documents for each signer.

Full Examples

The preceding code samples are illustrative. However, they are not really functional, since they contain placeholders like DOC1_ID, SIGNER1_ID, and packageID. To create functional code, those placeholders must be replaced with suitable values.

To view functional examples of the Document Visibility feature, please go to the following sites.

Java Code

https://github.com/eSignLive/esl.sdk.java/blob/11.5.1/sdk/src/main/java/com/silanis/esl/sdk/examples/DocumentVisibilityExample.java

C# Code

https://github.com/eSignLive/esl.sdk.net/blob/v11.16/sdk/SDK.Examples/src/DocumentVisibilityExample.cs

Video Tutorial

How to Use Document Visibility in OneSpan Sign