> 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

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.cerby.com/cerby-web-app/collections/managing-your-subcollections/remove-a-subcollection-from-a-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.