> 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/envelopes/how-to-add-or-remove-an-envelope-from-a-chain.md).
# How to Add or Remove an Envelope from a Chain
This document describes the process of managing envelope chains, including how to add individual envelopes to a chain, how to remove them, and how this affects chain order and workflow.
{% hint style="warning" %}
You can add an envelope to a chain only if it isn’t already in another chain.
{% endhint %}
### When to use this
Use chains when several envelopes belong to the same process and you want to keep them connected.
Common cases:
* continue one business process in a new envelope
* group related envelopes for easier tracking
* remove an envelope that was added to the wrong chain
### Add envelopes to a chain
1. Select the envelopes you want to chain.
2. Click the **Add envelope to chain**  icon.
#### Add to an existing chain (merge)
{% columns %}
{% column %}
Use this when the envelope you need isn’t on the same page.
1. Select an envelope.
2. Click the **Add envelope to chain** icon.
3. In the modal, enter the subject or UUID of the envelope you want to add, then confirm.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Remove envelopes from a chain
You can remove an envelope from a chain only if you added it to that chain.
1. In the envelopes list, select the chained envelope(s).
2. Click the **Remove envelope from chain** icon.
---
# 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/envelopes/how-to-add-or-remove-an-envelope-from-a-chain.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.
icon.
---
# 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/envelopes/how-to-add-or-remove-an-envelope-from-a-chain.md?ask=