> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/collections/collection-folders/create-a-folder-in-collection.md).

# Create a Folder in Collection

### **How to Create a Folder in Collection**

Users can create **Folders** within a Collection by following these steps:

#### **🔹 Step 1: Select Assets in Collection**

* Navigate to **Collections** and open the Collection that contains the assets you want to organize.
* Select the **Assets** you want to place into a folder.

<figure><img src="/files/x4UCFCpONWQkIuf3TU4V" alt=""><figcaption><p>Select Assets in Collection</p></figcaption></figure>

#### **🔹 Step 2: Create a New Folder or Choose an Existing One**

* Click on the **Folder** icon in the toolbar.
* Enter a **new Folder name** or select an existing Folder.

<figure><img src="/files/tbGBuoshtsRxmSjecAKu" alt=""><figcaption><p>Click on the <strong>Folder</strong> icon</p></figcaption></figure>

<figure><img src="/files/zZNxxKEzHINRWKSPccnl" alt=""><figcaption><p>Enter a <strong>new Folder name</strong> </p></figcaption></figure>

#### **🔹 Step 3: Confirm Folder Creation**

* Click **"Submit"** to complete the folder creation process and organize your assets.

### **Important Notes When Using Folders in Collections**

📌 **Collection folders can not have permissions set on them**. You can only set permission on the collection itself, which will automatically set asset permissions on all the assets inside the collection. [See Collection Permissions here](/collections/collection-permissions.md).\
📌 **Deleting a folder does not delete the assets inside**—they will still exist in the original Collection.\
📌 **Assets can be moved between folders** to optimize content organization.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/collections/collection-folders/create-a-folder-in-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.
