> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/initiate-and-sign-envelopes/creation-of-an-envelope/signing-flows/only-others-will-sign/sending-documents-to-others.md).
# Sending Documents to Others
### Sending Documents to Others
Once all participants are added, workflows are configured, and additional settings are completed, the initiator clicks **Next** to initiate the envelope.
In this flow, the initiator does **not** sign the document. Clicking **Next** directly sends the document to the configured participants for their signature or review.
***
### Envelope Initiation Confirmation
After the envelope is initiated, a confirmation screen is displayed indicating that the document has been successfully sent to participants for their signatures and reviews.
This message confirms that:
* The envelope has been created successfully
* The signing workflow has started
* Notifications have been triggered to all configured participants based on the defined workflow
***
### Email Notification to the Next Participant
Based on the configured workflow (serial or parallel), participants receive an email notification when it is their turn to act.
Each email contains:
* Document details (document name, sender, and date)
* A **Review and Sign** action button
This notification indicates that the document is pending the participant’s signature or review.
***
### Accessing the Document for Signing
When a participant clicks **Review and Sign**:
* **External participants** are taken directly to the document signing page via the secure signing link.
* **Internal participants** are redirected to the emSigner login screen and, upon successful login, are taken to the signing interface.
Once accessed, participants can review the document and proceed with their assigned action.
***
### Viewing the Signing Order
Participants can view the **Signer Order Diagram** to understand:
* Who initiated the document
* All participants involved in the workflow
* The current status of each participant (completed, pending, or not started)
This provides clear visibility into the overall signing progress and the position of the participant in the workflow.
***
### Completing the Signature
After reviewing the document, the participant:
* Applies their signature
* Clicks **Sign & Finish**
The document then progresses based on the workflow configuration:
* In **serial workflows**, the document is sent to the next participant in sequence.
* In **parallel workflows**, the document continues collecting signatures from remaining participants simultaneously.
***
### Completion of the Workflow
Once all participants have completed their actions:
* The document status is updated to **Completed**
* A completion email, along with the signed document and audit trail, is sent to **all participants**
* The signed document is available in **Doc Store** for future access
* Audit logs and signing details are preserved for compliance and verification
This marks the successful completion of the multi-participant signing workflow.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.emsigner.com/initiate-and-sign-envelopes/creation-of-an-envelope/signing-flows/only-others-will-sign/sending-documents-to-others.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.