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

# Reporting

Provides various reports to help manage and monitor account activity

⚠️ **User Right Required:** User must have the permission: **“Can View Reports Page"** to access **Reporting page.**&#x20;

HIVO Reporting provides insights into how Assets, content, users, and activities are managed and used across your Library. Reports help you understand information such as how many Assets you have, how Assets are being viewed or downloaded, which Assets are inactive, compliance status, user activity, and historical actions.

👉 To make reports easier to find, HIVO organises them into categories based on their purpose, making it easier to identify the report relevant to your goal.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4>Dashboard</h4></td><td>Overview of key reporting information across your HIVO Library</td></tr><tr><td><h4>Assets</h4></td><td>Understand your Asset volume, usage, and inactive Assets</td></tr><tr><td><h4>Compliance</h4></td><td>Monitor Archived Assets, Sensitive Assets, expired licences, and Consent status</td></tr><tr><td><h4>Content</h4></td><td>Review information relating to Templates, Collections, and Products</td></tr><tr><td><h4>Users</h4></td><td>Understand user rights, usage, inactive users, and recommendations</td></tr><tr><td><h4>Activity</h4></td><td>Review historical activity such as Library searches, uploads, Shared Links, Recognition activity, and deletions</td></tr></tbody></table>

#### 1. Show or hide the Report Navigation Panel

The Report Navigation Panel appears alongside the report and provides quick access to all available reports.

* Select the arrow icon (<) at the top of the panel to collapse it when you need more space to view report data. You can expand it again whenever you need to navigate to another report.
* You can also use Search reports to quickly find a report instead of browsing through each category.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FXHv0GiDYrPv1LBGXL5km%2FGroup%20820.png?alt=media&amp;token=7d7ce844-dea8-42db-8131-3a7e43ab56b1" alt=""><figcaption></figcaption></figure>

#### 2. Select a report to view

From the Report Navigation Panel, select the report you want to explore.

* Depending on the selected report, HIVO may provide additional controls such as date ranges, filters, sorting, result counts, and CSV export.
* For example, the Asset Usage report allows you to see how individual Assets are being used, including:
  * *Download Count In-app*&#x20;
  * *View Count Shared*&#x20;
  * *View Count Shared Embedded*&#x20;
  * *View Count*&#x20;
  * *Total View Count*

You can use this information to identify frequently used Assets, understand how content is being accessed, and make better decisions about how your Library is managed.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F7qSnNItMyOt1CJClxDTY%2FGroup%20821.png?alt=media&amp;token=8a3aaf86-269a-4ea3-92b3-915835125f85" 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 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/reporting.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.
