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

# Collections

A **Collection** is a feature that allows users to group **digital assets** (images, videos, documents, etc.) based on specific purposes such as projects, campaigns, or topics. It is the central unit of organization in the system, helping you manage assets effectively and flexibly.

**For example:**

* Collection "Photo of project 06/06/2024"
* "Site Graphics 2024" Collection

### **What does a Collection include?**

A Collection consists of the following components:

* **Main Page: Collection Page**\
  This is the page where all Collections that you have access to are listed.
* **Detail Page: Collection Detail Page**\
  The interface showing detailed content of a specific Collection (assets, description, permissions, etc.).
* **Categories**\
  Allows you to group Collections into categories for better organization.
* **Collection Info (Edit Info)**\
  Includes: name, description, owner, tags, category, thumbnail,...
* **Permissions**\
  Define who can view, edit, or download assets in the Collection.
* **Automations**\
  Allows you to set up automated rules. If any uploaded asset matches the conditions in the rule, the system will automatically add that asset to the corresponding Collection.
* **Public Collection**\
  Public view allows visitors to access this collection.


---

# 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.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.