> 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.md).

# Grouped Collections

Manage and share multiple asset collections simultaneously, optimizing workflows between businesses and partners.

**Grouped Collections** is a feature that allows users to group multiple individual collections together for centralized management. This enables **sharing multiple collections** simultaneously with partners, clients, or internal departments, instead of having to manually share each separate link.&#x20;

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F2oyKMLlO6FRguW8uBhrI%2Fimage%20401.png?alt=media&amp;token=0eb01a6d-7d72-4c86-a7e4-ba4eb93de2a0" alt=""><figcaption></figcaption></figure>

#### **🔹** Key functional include:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4>Administration &#x26; Navigation</h4></td><td>View lists, perform smart searches, and filter, sorting groups flexibly.</td></tr><tr><td><h4>Content Structure Management</h4></td><td>Create new groups, duplicate entire group structures, or edit internal categories to classify assets.</td></tr><tr><td><h4>Sharing &#x26; Access Control</h4></td><td>Create secure sharing links and track performance based on view counts.</td></tr><tr><td><h4>Share Link Management</h4></td><td>Take full control of all published links: Monitor expiration dates, quick copy, edit permissions, or instantly revoke links.</td></tr><tr><td><h4>Collaboration &#x26; Feedback</h4></td><td>Comment directly on assets, hold discussions, and mark statuses as "Resolved" or "Request Change".</td></tr><tr><td><h4>Personalized Display Settings</h4></td><td>Customize how sub-collections are displayed in a grid view, adjust sizes, etc.</td></tr></tbody></table>

#### **🔹** Business Use Case:

* **Cross-platform Marketing Campaigns:** When running a major campaign, the Marketing team needs to simultaneously share multiple distinct asset collections with external agencies, such as Product Photos (Collection A), Promotional Videos (Collection B), and Banner Mockups (Collection C). This feature packages everything into a single, unified link.
* **Project Handover to Clients:** The Account or Technical teams need to deliver project outputs categorized into separate sections while ensuring a cohesive, professional presentation within a single shared space.
* **Internal Management by Departmental Structure:** Consolidate assets based on functional groups (for example, an HR Resource Group comprising Event Photos, Onboarding Documents, and Training Videos).


---

# 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://support.hivo.co/grouped-collections.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.
