> 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/what-are-the-different-asset-permission-tiers.md).

# What are the different Asset Permission Tiers?

In HIVO, permission tiers control what a user/group can do with an asset (and similarly with folders/collections). All tiers include viewing permissions.

## Asset Permission Tiers

To check the permissions for yourself or other members on a specific asset, follow these steps:

👉 How to access: Go to the Asset Detail page ➔ **Permissions** (gear icon → **Permissions** tab), the tiers are:

* **Can View:** Allows users to view the asset. 
  * For assets with special conditions (such as *Archived*, *Sensitive*, or other restricted states), users must have the corresponding permissions to view them.
  * Similarly, if a user or user group is not permitted to view unapproved versions (*Not restricted to Approved-Only Versions*), they will need to submit a Review Request to gain access to those restricted versions.
* **Can Share:** Allows users to share the asset with others. 
* **Can Edit**: Allows users to edit asset details and information.
  * Advanced: If a user or user group also holds the Can Edit Asset Permissions right, they can modify the access permissions for this asset (provided they currently have Full Access to it).
* **Add Versions:** Allows users to upload and add new versions to an existing asset.
  * Users must be granted the Can Upload Asset Versions permission to perform this action.
* **Full Access:** Grants users full control to perform all the actions above (including: View, Share, Edit, and Add Versions).

👉 See more about [**Assets Permission**](https://support.hivo.co/assets/assets-permission) here. 

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/faqs/what-are-the-different-asset-permission-tiers.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.