> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-web-app/collections/managing-your-subcollections/remove-a-subcollection-from-a-collection.md).

# Remove a subcollection from a collection

This article describes how to remove a subcollection from a collection, thus converting it to a root collection.

To remove a subcollection from a collection, you must complete the following steps:

1. Log in to your corresponding [Cerby](https://app.cerby.com/) workspace.
2. Select the **Collections** option from the left navigation drawer. The **Collections** page is displayed.
3. Expand the collection that contains the subcollection you want to remove.
   * Alternatively, you can search for the subcollection in the search bar.
4. Hover the mouse over the subcollection you want to share. A menu of icons is displayed.
5. Click the **More options** (...) icon. A menu is displayed.
6. Select the **Remove from collection** option. The **Remove subcollection from collection?** dialog box is displayed with the information about what occurs when you remove a subcollection from a collection.
7. Click the **Remove subcollection** button. The dialog box closes, a success message box is displayed, and an email message is sent.


---

# 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://help.cerby.com/cerby-web-app/collections/managing-your-subcollections/remove-a-subcollection-from-a-collection.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.