> 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/faqs/hivo-best-practice-for-organising-assets-in-the-library-versus-collections.md).

# HIVO best practice for organising Assets in the Library versus Collections

### **🔹** Library Best Practices

Treat the **Library as the single source of truth**: Assets are stored only once, in the Library. Collections then reference those assets without duplicating them.

* **Use Library Folders** to keep the **underlying asset storage tidy** (and scalable): You can create folders and subfolders from the Library.
* Pick the right [**Library View Mode**](https://support.hivo.co/library/library-view-modes)**:**

  * **Asset view**: For seeing each asset in detail and reviewing its content directly.
  * **Folder view**: For browsing folders and quickly navigating broad categories.
  * **Tree view**: For hierarchical folder navigation.
  * **Map view:** For viewing assets by their upload location.

If you’re trying to optimise your workflow, also check [**Library Settings**](https://support.hivo.co/library/library-settings) for display mode and browsing preferences.

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

### **🔹** Collections Best Practices&#x20;

*(For organising image sets)*

* Use a [**Collection**](https://support.hivo.co/collections/create-new-a-collection) to group assets by purpose (project, campaign, topic) so they’re easier to manage and access.
* For big collections, use [**Collection Folders**](https://support.hivo.co/collections/collection-folders) to organise assets within the collection (they’re different from Library folders).
* For large numbers of collections, use [**Collection Categories**](https://support.hivo.co/collections/collection-categories) (hierarchical parent → sub-category) and optionally tags for filtering/search.

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

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/faqs/hivo-best-practice-for-organising-assets-in-the-library-versus-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.