> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-change-a-capsule-collection-or-group.md).
# How to change a Capsule collection or group
Learn how to move a Capsule from one collection or group to another.
Follow these steps to change the Capsule collection or group:
{% hint style="info" %}
The name of the Capsule must be unique within the collection, so a Capsule can’t be moved to another collection that has a different Capsule with the same name. Note that the name of the Capsule is different from the title, as the title is displayed in the Capsules list and the name is the identifier that ensures that Capsules can't be named the same within a collection.
{% endhint %}
1. On the **Build** page, click the **Capsules** tab.
2. Move the mouse pointer over the Capsule you want to move. A draggable icon will appear in the bottom right corner of the card.
3. Hold down the mouse button over the icon and drag the Capsule to the collection or group you want to move to. If the Capsule has more than one version, regardless of whether they are archived or not, all versions are moved together. The archived versions remain archived.
4. A confirmation message will appear on the screen. Check the information and click **Move** to confirm the action.
---
# 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://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-change-a-capsule-collection-or-group.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.
