> 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/delete-a-subcollection.md).

# Delete a subcollection

This article describes how to delete a subcollection from a parent collection, removing inherited access from top-level collections.

To delete a subcollection, you must complete the following steps:

{% hint style="danger" %}
**IMPORTANT:** To delete a subcollection, you must have access as **Owner** to the settings of its parent collection.
{% endhint %}

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 **Delete collection** option. The **Delete collection?** dialog box is displayed.
7. Select how you want to delete the collection:
   * **Keep account permissions for the same users and teams:** You will delete the subcollection but maintain the account, secrets, and subcollections within it in Cerby. When you select this option, the subcollections inside become root collections and are displayed on the **Collections** page.
   * **Delete all items in the collection:** You will delete all accounts, secrets, and subcollections inside it. When you choose this option, another **Delete collection?** dialog box is displayed. Click the **Delete all items** button to delete all items.

{% hint style="warning" %}
**IMPORTANT:** Be careful when selecting this option. It is not possible to recover the items later.
{% endhint %}


---

# 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/delete-a-subcollection.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.