> 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

# Suppressed features and behaviors

This section describes features and behaviors that are characteristic of Remote Recipients but not applicable to Embedded Recipients.

1. Carbon-Copy Recipients cannot interact as Embedded Recipients. Embedded Recipients are not presented with the option to create a Password in Docusign. Consequently, Captive Recipients cannot enter the Docusign web application via the [login screen](https://account.docusign.com/). Captive Recipients can only enter Docusign via client applications using Recipient Tokens.
2. Embedded Recipients do not see the Docusign Member Console.
3. Embedded Recipients do not receive Docusign-generated email notification for any events except for the Signing/Viewing confirmation upon completion of the respective task, described in the Additional Features/Benefits section.