> 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/history.md). # History To help with tracking account activity and ensuring correct usage, actions on assets, collections, and tasks are logged as history entries on their respective entities. Here's how you can access and use these history logs. ### Accessing History on Assets To view the history of an asset: 1. Navigate Asset's details page. 2. Click the clock icon on the Asset's details page. You'll see a list of all actions, who made the changes, and a timestamp.

### Accessing History on Tasks To view the history of a task: 1. Navigate to the Task Detail Page 2. Click the clock icon to see the list of all actions, who made the changes, and a timestamp.

### Accessing History on Collections To view the history of a collection: 1. Navigate to the Collection Detail page. 2. Click the three dots ‘settings’ icon. 3. Select the History tab to see all actions, who made the changes, and a timestamp.

### Viewing Comprehensive History Logs Administrators have access to a full list of history entries across all assets, collections, and tasks. To access these logs: 1. Go to Reporting: Reporting is accessible through the left navigation bar for Administrator accounts. 2. Select historical report, you can view report according to a specific time period.

By effectively utilizing these history logs, you can ensure accurate tracking of account activity --- # 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/history.md?ask=&goal= ``` `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.