> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Supplemental Documents

> Describes the concept of and options for including supplemental documents in an envelope.

*Supplemental documents* are supporting materials, such as disclosures or informational documents, that recipients can view and acknowledge but do not need to sign.

You can identify a document as supplemental by checking its `display` property. If the `display` property has a value of `modal`, the document is considered supplemental.

Supplemental documents use the following properties in the `document` object:

| Property                | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `includeInDownload`     | Determines whether the supplemental document is included in the combined document download.                                                                                                                                                                                                                                                                                                                                                                    |
| `display`               | Specifies how the supplemental document is displayed to the recipient. The possible values are:- `modal` The document appears in a modal window as a supplement action strip. Recipients can view, download, or print it. This is the recommended value for supplemental documents.
- `inline` The document is displayed in the normal signing window. This value is typically not used for supplemental documents but is the default for all other documents. |
| `signerMustAcknowledge` | Indicates whether the signer must acknowledge the supplemental document if they do not have Approve and View tabs.                                                                                                                                                                                                                                                                                                                                             |

If a signer does not have **Approve** and **View** tabs, the value of the `signerMustAcknowledge` property determines the required interaction with the supplemental document:

| `signerMustAcknowledge` | Signer Action                                        |
| ----------------------- | ---------------------------------------------------- |
| `no_interaction`        | No action is required.                               |
| `view`                  | The signer must view the document.                   |
| `accept`                | The signer must accept the document.                 |
| `view_accept`           | The signer must view and accept the document.        |
| `view_read_accept`      | The signer must view, read, and accept the document. |

If the signer has **Approve** and **View** tabs, the platform disregards the `signerMustAcknowledge` property and instead uses the values of these tabs to determine signer requirements:

| Approve Tab is present | View Tab's requiredRead Property | View Tab's required Property | Signer Action                                        |
| ---------------------- | -------------------------------- | ---------------------------- | ---------------------------------------------------- |
| No                     | `false` (default)                | `false` (default)            | No requirements.                                     |
| No                     | `false`                          | `true`                       | The signer must view the document.                   |
| No                     | `true`                           | --                           | The signer must view and read the document.          |
| Yes                    | `false`                          | `false`                      | The signer must view and accept the document.        |
| Yes                    | `false`                          | `true`                       | The signer must view and accept the document.        |
| Yes                    | `true`                           | --                           | The signer must view, read, and accept the document. |

> **Note:** The `requiredRead` property of a Viewtab takes precedence over its `required` property. If `requiredRead` is set to `true`, the platform assumes `required` is also true.