> 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 # Recipients > Learn about recipients, how they fit into the eSignature workflow, and about commonly-used recipient functionality. ## Recipients A *recipient* object refers to a person who receives a Docusign [envelope](/docs/esign-rest-api/esign101/concepts/envelopes). Each envelope object must have one or more recipients, and each recipient may have one or more [Tabs](/docs/esign-rest-api/esign101/concepts/tabs) (also known as *fields* or *tags*) defined for them. Each recipient is assigned a specific type, which defines their role in the signing process (see [EnvelopeRecipients](/docs/esign-rest-api/reference/Envelopes/EnvelopeRecipients) for details on each type). Any of these recipients can be a *remote recipient* (who receives the envelope via email), or an *embedded recipient* (who views, approves, or signs the envelope’s documents directly through your app or website). > **Note** > > For examples of how to work with recipients using the API, see how to assign roles to a recipient and [How to request a signature by email](/docs/esign-rest-api/how-to/request-signature-email-remote). The following diagram shows the structure of a recipient object, and how it relates to envelopes and documents. ![Envelope structure graphic](/_fern-files/_img/1d54b54124c0cffd50cba53d93f18d851fb904cad97074ec0ad2f9581e057a09.webp) ## Recipient types Each recipient of a Docusign envelope is assigned a specific type that defines their responsibilities in the signing process. Each recipient type and the responsibilities associated with that type are described by the following table. The **Name in the UI** column contains the label used for the recipient type in the [eSignature web app](https://apps-d.docusign.com/send/documents/). | Recipient type | Name in the UI | Description | | ---------------------------------------------------------------------------------------------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Agents](/docs/esign-rest-api/reference/envelopes/enveloperecipients#agent-recipient) | Specify Recipients | An agent recipient can add name and email information for recipients that appear after the agent in the routing order. You can use this recipient type to designate an agent or manager to set your recipients when you do not know who the eventual signers will be. | | [Carbon Copies](/docs/esign-rest-api/reference/envelopes/enveloperecipients#carbon-copy-recipient) | Receives a Copy | Carbon copy recipients get a copy of the envelope but don't need to sign, initial, date, or add information to any of the documents. This type of recipient can be used in any routing order. Carbon copy recipients receive their copy when the envelope reaches the recipient's order in the process flow and when the envelope is completed. | | [Certified Deliveries](/docs/esign-rest-api/reference/envelopes/enveloperecipients#certified-delivery-recipient) | Needs to View | Certified delivery recipients must receive the completed documents for the envelope to be completed. However, they don't need to sign, initial, date, or add information to any of the documents. | | [Editors](/docs/esign-rest-api/reference/envelopes/enveloperecipients#editor-recipient) | Allow to Edit | Editors have the same management and access rights for the envelope as the sender. They can make changes to the envelope as if they were using the Correct feature. This recipient can add name and email information, add or change the routing order, and set authentication options for the remaining recipients. Additionally, this recipient can edit signature/initial tabs and text tabs for the remaining recipients. The recipient must have a Docusign account to be an editor. | | [In Person Signers](/docs/esign-rest-api/reference/envelopes/enveloperecipients#in-person-signer-recipient) | In Person Signer | An in person signer recipient is a Docusign user who is in the same physical location as the signer. | | [Intermediaries](/docs/esign-rest-api/reference/envelopes/enveloperecipients#intermediary-recipient) | Update Recipients | An intermediary is a recipient who can, but is not required to, add name and email information for recipients at the same or subsequent level in the routing order, unless subsequent agents, editors, or intermediaries are added. You can use this recipient type to set up a recipient as a reviewer of your signer's information. They can specify details for role recipients and update information for named recipients. | | [Notary recipients](/docs/notary-api/notary101/concepts/notary-recipients) | Signs with Notary | Notaries are a specialized type of recipient that is new with the Notary API, enabling you to notarize documents remotely by having a notary public act as an in-person (online) witness to the electronic signing. | | [Seals](/docs/esign-rest-api/reference/envelopes/enveloperecipients#seal-recipient) | Electronic Seal | Electronic seal recipients represent legal entities rather than individuals. [Electronic seals](https://support.docusign.com/s/document-item?language=en_US\&rsc_301\&bundleId=xcm1643837555908\&topicId=isl1578456577247.html&_LANG=enus) can be used by organizations and governments to show evidence of origin and integrity of documents. | | [Signers](/docs/esign-rest-api/reference/envelopes/enveloperecipients#signer-recipient) | Needs to Sign | A signer is a recipient who must sign, initial, date, or add data to text tabs on the documents in the envelope. | | [Witness](https://support.docusign.com/s/articles/DocuSign-eWitness?language=en_US\&rsc_301) | Signs with Witness | A [Witness](https://support.docusign.com/s/articles/DocuSign-eWitness?language=en_US\&rsc_301) is a recipient who must view and corroborate that a signer has provided their signature. | For details on recipient objects and types, see [EnvelopeRecipients](/docs/esign-rest-api/reference/Envelopes/EnvelopeRecipients). Not all recipients are available to all account types. Review your account plan to determine which recipient types are available to you. All recipient types are available in the [developer environment](https://account-d.docusign.com/). ## Next steps Read about important recipient features: * [Recipient authentication](/docs/esign-rest-api/esign101/concepts/recipients/auth) * [Scheduled sending](/docs/esign-rest-api/esign101/concepts/recipients/scheduled-sending) * [Delayed routing](/docs/esign-rest-api/esign101/concepts/recipients/delayed-routing) * [Pause and unpause a signature workflow](/docs/esign-rest-api/esign101/concepts/recipients/pause-unpause-workflow) * [Specify conditional recipients](/docs/esign-rest-api/esign101/concepts/recipients/conditional-recipients) Working with recipients? Learn how to: * Retrieve and interpret [recipient status codes](/docs/esign-rest-api/esign101/concepts/recipients/status-codes) * Handle [error codes](/docs/esign-rest-api/esign101/error-codes) * Assign roles to a recipient and [How to request a signature by email](/docs/esign-rest-api/how-to/request-signature-email-remote) * Add [Recipient authentication](/docs/esign-rest-api/esign101/concepts/recipients/auth) * [How to require phone authentication for a recipient](/docs/esign-rest-api/how-to/phone-auth) * [How to require ID verification (IDV) for a recipient](/docs/esign-rest-api/how-to/id-verification) * [How to require knowledge-based authentication (KBA) for a recipient](/docs/esign-rest-api/how-to/knowledge-based-authentication) * [How to require access code authentication for a recipient](/docs/esign-rest-api/how-to/require-access-code-recipient) > Learn about recipients, how they fit into the eSignature workflow, and about commonly-used recipient functionality. ## Docs - [Recipient authentication](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/auth.md): Learn about the methods that recipients can authenticate their identities during the signing ceremony, & how your app can implement these authentication methods. - [Scheduled sending](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/scheduled-sending.md): The Advanced Recipient Routing (ARR) features let you control the flow of envelopes through the signature process by scheduling an envelope to be sent automatically at a specific time. - [Delayed routing](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/delayed-routing.md): Docusign Advanced Recipient Routing (ARR) features let you control the flow of envelopes through the signature process by setting delays between steps in the routing order. - [Pause and unpause a signature workflow](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/pause-unpause-workflow.md): The Advanced Recipient Routing (ARR) features let you control the flow of envelopes through the signature process by pausing and unpausing envelopes. - [Specify conditional recipients](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/conditional-recipients.md): Docusign's Advanced Recipient Routing (ARR) features let you control the flow of envelopes by specifying different recipients to sign a document based on different conditions. - [Recipient status codes](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/recipients/status-codes.md): Learn about eSignature REST API recipient statuses.