> 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-create-a-capsule-collection.md).
# How to create a Capsule collection
Learn how to create a Capsule collection in the Digibee Integration Platform.
Collections are repositories where Capsules are stored.
Follow these steps to create a collection:
{% hint style="info" %}
If you don’t create a collection, the Capsule is saved in the **Default** collection. You can [move the Capsule to another collection](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-change-a-capsule-collection-or-group.md) after you have saved it.
{% endhint %}
1. On the **Build** page, click the **Capsules** tab.
2. Click the **Create** **new** button in the upper right corner.
3. Select the **Create Collection** option.
4. In the configuration form, fill in the **Collection name** and **Collection description** fields.
5. Activate the **Open Collection** option to allow users outside your organization to use the Capsules in the collection. Otherwise, leave the option deactivated.
6. In the **Header** section, select an existing header from the list. Headers help identify the collection to which a Capsule belongs. To add a new header to the list, you must perform the following steps:
1. Click on **Settings** in the upper right corner of the platform’s home page.
2. Open the **Capsules** option in the left sidebar.
3. Click **Create** to add the header. Learn more about the [Capsule header dimensions](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection/capsule-header-dimensions.md).
4. Once you have added the header, you can select it in the collection creation form.
7. In **Background color**, select a color that represents the collection. This color will be used in the icons of the Capsules after they are saved.
8. Click **Save** to add the new collection to the list in the left sidebar.
Once the collection is created, move the mouse pointer to the collection name in the left sidebar and click the three-dot icon button to display the following options:
* **Edit collection:** Edit the collection’s configuration form.
* **Delete collection:** Delete the collection. Only collections without active Capsules can be deleted.
* **Create group:** Create a [new group](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-group.md) within the collection.
---
# 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-create-a-capsule-collection.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.
