> 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/envelope-flow-statuses.md).

# Envelope Flow Statuses

This document explains the envelope states related to invitations in DocStudio.

{% hint style="info" %}
See the [Glossary](https://support.docstudio.com/glossary/glossary.md) for DocStudio term definitions.
{% endhint %}

### When an invitation envelope ends

An envelope sent via an email invitation can end in these cases:

* The participant accepts the invitation and then **completes** or **rejects** the envelope.
* The participant never accepts the invitation, and the envelope becomes **Expired** after the expiration date.
  * This happens only if the template has an expiration date configured.
* The sender or another participant in the flow **rejects** the envelope.

{% hint style="info" %}
**Expired** means the invitation was not accepted before the configured expiration date.
{% 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/envelope-flow-statuses.md?ask=<question>&goal=<user_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.
