> 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/how-to-add-asset-s-to-the-collection-s/automatically-add-assets-to-a-collection-via-rule-settings.md).

# Automatically add assets to a Collection (via rule settings)

Automated Collections can be used by Admin accounts to help facilitate the process of creating themed Collections.

The **Automated Collection** feature allows Admins to quickly and automatically add assets to collections. Instead of manually selecting each Asset to add to a Collection, you can set up **automation rules**. When an Asset is uploaded and meets the defined conditions, the system will automatically add that Asset to the corresponding Collection.

#### ✨ **Key Benefits**

* Save time on asset categorization.
* Ensure consistency in data organization.
* Reduce errors from manual asset selection.
* Automatically organize assets into themes such as events, key people, locations, content types, etc.

### **How to Set Up an Automated Collection**

To set up Automated Collection, follow these steps:

* Step 1: Go to the **Collection Detail** page.
* Step 2: Click on the **three-dot Settings icon** in the top right corner.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FFWn4h9dbyVKP0x9NM0ur%2FGroup%20843.png?alt=media&amp;token=f65c3802-c5ba-43df-bf61-d364a61f4281" alt=""><figcaption><p>Open "Collection Setting"</p></figcaption></figure>

* Step 3: Select the **Automations** tab and start creating rules to define the conditions assets must meet.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FKp2iuqri0uD1AZfHAeP5%2FGroup%20844.png?alt=media&amp;token=d4fbe0b3-fc70-439c-8cc9-2b7b0a142d3d" alt=""><figcaption></figcaption></figure>

📌 **Types of Conditions You Can Use in a Rule**

<table><thead><tr><th width="170.0025634765625">Condition</th><th>Description</th></tr></thead><tbody><tr><td><strong>Tags</strong></td><td>The asset must include at least one or all of the <strong>Must Match</strong> tags, and none of the <strong>Must Not Match</strong> tags.</td></tr><tr><td><strong>Production Date</strong></td><td>The asset must have a production date within the selected date range.</td></tr><tr><td><strong>Location</strong></td><td>The asset must contain GPS coordinates that fall within a defined location.</td></tr><tr><td><strong>Type</strong></td><td>The asset must match the selected file type (e.g., image, video, etc.).</td></tr><tr><td><strong>Face</strong></td><td>The asset must contain the face(s) of one or more people specified in the collection.</td></tr></tbody></table>

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F9iOkkD8oA3oVJEuDexo5%2FGroup%20845.png?alt=media&amp;token=cab38cb6-52cd-402d-ae46-33d1b3dbcb02" alt=""><figcaption><p>Apply location</p></figcaption></figure>

#### **Must Match and Must Not Match Tags**

Tags you type into a rule are **Must Match** tags by default. To exclude assets with a certain tag, click the arrow on that tag and choose an option:

<table><thead><tr><th width="170">Option</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Must Match</strong></td><td>The asset must have this tag. Use the options below the tags to choose whether the asset needs <strong>at least one</strong> or <strong>all</strong> of the Must Match tags.</td></tr><tr><td><strong>Must Not Match</strong></td><td>Assets with this tag don't match the rule. The tag is shown with a red outline and crossed out.</td></tr><tr><td><strong>Remove</strong></td><td>Removes the tag from the rule.</td></tr></tbody></table>

* A rule with only Must Not Match tags matches every asset that has none of those tags (as long as the rule's other conditions are met).
* Must Not Match tags also work the same way in **SKU** automation rules.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FoLKDiZtmPG7i6j5pZ48K%2FGroup%201154.png?alt=media&amp;token=fb435700-0509-4511-a5a2-442ef55d4af6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Must Not Match only stops automations from adding assets. It doesn't stop you from uploading or adding assets to a Collection yourself.

Automations also only add assets. If an asset is already in the Collection and later gets a Must Not Match tag, it isn't removed from the Collection automatically.
{% endhint %}

### **How Automation Rules Work**

* Each rule contains multiple condition fields (e.g., tags, production date, face detection, etc.). Any field left empty will be ignored.
* An asset must meet **all non-empty conditions** in a single rule to be added to the Collection. An asset with any of the rule's **Must Not Match** tags never meets that rule.
* If there are multiple rules:\
  ➤ **If any uploaded Assets match one of the rules listed below, the Asset will be added to this Collection.** An asset excluded by one rule can still be added through another rule it matches.

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 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/collections/how-to-add-asset-s-to-the-collection-s/automatically-add-assets-to-a-collection-via-rule-settings.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.
