> 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/grouped-collections/duplicating-and-remove-a-grouped-collection.md).

# Duplicating & Remove a Grouped Collection

These features allow you to quickly duplicate or remove grouped collections based on a simple rule:

* [**When duplicating**](#duplicating-a-grouped-collection): You can flexibly choose to replicate the entire structure along with its internal sub-collections, or just copy an "empty framework" to use as a template for a new group.
* [**When removing**](#remove-grouped-collection): The system only deletes the outer wrapper, with zero risk of affecting or losing your internal sub-collections and original assets.

👉 Below is a step-by-step guide to help you quickly duplicate existing group structures or remove groups that are no longer needed, optimizing your setup time and keeping your workspace clean.

### Duplicating a Grouped Collection&#x20;

⚠️ **User Right Required:** User must have the permission: **“*****Can View All Grouped Collections***" and "**Can Insert Grouped Collections**".&#x20;

<figure><img src="/files/4PuefaaKU4Wuub8lqLSo" alt=""><figcaption></figcaption></figure>

When you want to create a new group with a structure similar to an existing one:

* Click the three vertical dots **(⋮)** **icon** at the bottom right corner of the Grouped Collection's thumbnail.
* Select **Duplicate Grouped Collections** to open the dialog box.

<figure><img src="/files/R07ouGs8gFXDxEnoia4W" alt=""><figcaption></figcaption></figure>

* Label: **Enter a name** for the new grouped collection.
* "**Duplicate Inner Collections & Categories**" option:
  * **If Checked:** The system will copy all sub-collections and the internal category structure into the new group.
  * **If Unchecked:** The newly created group will be completely empty, and you will need to manually add sub-collections and categories later.
* Click **Submit** to complete the process.

<figure><img src="/files/druAyjszHHoUK0c6toSF" alt=""><figcaption></figcaption></figure>

### Remove Grouped Collection

⚠️ **User Right Required:** User must have the permission: **“*****Can View All Grouped Collections***" and "***Can Remove All Grouped Collections***".

<figure><img src="/files/LhTBavl6KNJxZzIuKKk0" alt=""><figcaption></figcaption></figure>

When centralized management is no longer needed, you can dismiss one or multiple structural groups:

* Click to select one or more **Grouped Collections** you wish to delete (or use **Select All** to select all).
* Click the **Remove** button on the toolbar. The system will immediately remove the selected Grouped Collections from the general dashboard.

<figure><img src="/files/f5hMO1hmm2jJiJOG3MrO" alt=""><figcaption></figcaption></figure>

📌 Note: This action only deletes the "outer wrapper group structure". It will absolutely Not Delete, hide, or affect of the internal sub-collections or their assets.

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/grouped-collections/duplicating-and-remove-a-grouped-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.
