> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/envelope-invitations-and-completion/how-to-invite-an-unregistered-recipient-to-an-envelope-by-email.md).
# How to Invite an Unregistered Recipient to an Envelope by Email
This document explains how to email an invitation to a participant from the envelope draft page.
### Invite a participant by email (from a draft)
1. Open an envelope draft without a predefined processing flow.
2. In the role field, enter the participant’s email address.
3. If the flow has inherited roles, the email is applied to them automatically.
4. Finish configuring the envelope.
5. Click the 
button.
6. In the confirmation dialog, review the warning about sending to an email address.
7. Confirm to send the envelope.
{% hint style="info" %}
When you enter an email address, you don’t need to select a mailbox from the dropdown.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.docstudio.com/user/envelope-invitations-and-completion/how-to-invite-an-unregistered-recipient-to-an-envelope-by-email.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.