> 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/assets/assets-permission.md).

# Assets Permission

Asset permissions in HIVO are essential for controlling who can view and modify assets and to what extent. This guide will help you understand and manage asset permissions effectively.

### **Overview of Asset Permissions**

Permissions determine user access to assets and their versions. When a user has access to an asset, they generally have access to all versions within that asset. However, if the user’s ‘***Can View Image Original Versions***’ right is toggled off, they will only see non-original, watermarked versions. This setting is often used alongside watermarking to restrict access. For more information on watermarking, see the relevant section. See more "[Edit User Rights](https://support.hivo.co/client-profile/users/list-of-user-rights)" here.&#x20;

<figure><img src="/files/7kJ7LL0Dw2nUm47Wy1V2" alt=""><figcaption><p>Asset Permission</p></figcaption></figure>

### **Viewing and Editing Permissions**

You can view and edit asset permissions on the ‘Permissions’ tab of the Asset Detail page, accessed via the gear icon.&#x20;

* This tab shows the access levels of all users, including those with inherited permissions from Collections.&#x20;
* To modify permissions, click the ‘Permissions’ heading to open a popup.&#x20;

<figure><img src="/files/iMsKneYgAQXnw1kmghjU" alt=""><figcaption><p>Edit Asset Permission</p></figcaption></figure>

👉 **Note that:** *Permissions inherited from Collections must be changed within the Collection itself.*

### **Permission Tiers Explained**

All permission tiers grant viewing permissions for the asset. Here’s a breakdown of the additional permissions each tier provides:

* **Can View**: Users can view the asset and its versions.
* **Can Share**: Users can share the asset with others.
* **Can Edit**: Users can make changes to the asset.
* **Add Versions**: Users can add new versions to the asset.
* **Full Access**: Users have all permissions, including viewing, sharing, editing, and adding versions.

### **Modifying Permissions for Multiple Assets**

To change permissions for multiple assets simultaneously, use Library Actions. This feature allows for bulk editing, saving time and ensuring consistency across your assets.

<figure><img src="/files/ADjTyVcgXF3apnqs9DyF" alt=""><figcaption><p>Edit Permission for Multiple Assets</p></figcaption></figure>

**Key Points to Remember**

* Users with access to an asset can view all versions unless restricted by the ‘Can View Originals’ right.
* Permissions can be viewed and edited on the Asset Detail page under the ‘Permissions’ tab.
* To modify permissions for multiple assets, use Library Actions.
* Different permission tiers provide varying levels of access, with ‘Full Access’ granting complete control.

By managing asset permissions in HIVO, you can ensure that your assets are secure and accessible to the right users.


---

# 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/assets/assets-permission.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.
