> 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/~/changes/eaCuYFhybbREuBouwZp6/assets/asset-detail-page.md).

# Asset Detail Page

To reach the Detail Page of an Asset, either double click the Asset to open the Asset Preview and then click the Asset title, or click the down arrow on the Asset thumbnail in the Library and then select ‘View Details’.

<figure><img src="/files/nt2WEtfSCLMqW9pzOY8Y" alt="View asset details"><figcaption><p>View asset details</p></figcaption></figure>

An example Asset Detail Page can be seen below:

<figure><img src="/files/zmCjeIFQdYreHYh3ONPK" alt="Asset detail page"><figcaption><p>Asset detail page</p></figcaption></figure>

### Commenting on Assets

At the bottom of the Asset Detail page is a comments section, where you’ll see all comments made by Users on the Asset. You can create a comment using the ‘New Comment’ section, which has several markdown options along the top. Click the speech bubble icon to **mention another User**, and notify them about the comment.

<figure><img src="/files/RbaIiCnXB7r7jj2VNF04" alt="new comment"><figcaption><p>New comment</p></figcaption></figure>

For image, PDF and video Assets, **you can create comments by clicking directly on the Asset**. Video comments are placed on a timestamp within the video and remain for a few seconds after. You can jump to a comment made on the video by clicking the comment icons placed along the timeline bar. Each User has a unique color for these icons.

<figure><img src="/files/vawOsoRjZfrGrsjI0c5G" alt="Video comment"><figcaption><p>Video comment</p></figcaption></figure>

Comments are tied to a Version of the Asset, and aren’t shared between Versions. All existing comments will appear above the ‘New Comment’ section, and can be edited, deleted or replied to. Users will only be able to edit the contents of their own comments, and Admin accounts will be able to delete all comments.

### Asset Permissions

Asset permissions determine who can view and modify a given Asset, and to what extent. If a user has access to an Asset, this includes all Versions within that Asset, unless the user has the ‘Can View Originals’ user right toggled off. This right is most commonly used in conjunction with watermarking settings to restrict a user's access to only non-original watermarked versions. [See: Watermarking](/~/changes/eaCuYFhybbREuBouwZp6/assets/watermarking.md) for more information.

Permissions for an Asset **can be viewed and edited on the ‘Permissions’ tab of the Asset Detail page** (gear icon). Under this tab will be the access level of all users, including those that have inherited permissions from Collections. Click the ‘Permissions’ heading in this tab to open up a popup to modify access (note: permissions inherited from Collections have to be changed from the Collection). To modify the permissions of multiple Assets at once, use [Library Actions](/~/changes/eaCuYFhybbREuBouwZp6/library/library-actions.md).

All permission tiers (can view, can share, can edit, add versions, full access) grant viewing permissions on the asset. The ‘Can Share’, ‘Can Edit’ and ‘Add Versions’ permissions only grant additional permissions to their namesake.

<figure><img src="/files/n7sspW7qoIAEzu0DALuP" alt="Asset permissions"><figcaption><p>Asset permissions</p></figcaption></figure>


---

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

```
GET https://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/assets/asset-detail-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
