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

# Approvals

The Approval section of HIVO provides a comprehensive set of tools for managing and tracking the digital asset workflow. Its main function is to ensure quality, compliance, and consensus before an asset is published or used. It controls every stage, from when the asset is uploaded and edited, to the confirmation of usage rights and granting access to the version.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Upload Approvals</h3></td><td>Manage all newly uploaded assets before they become visible in the Library</td><td><a href="https://support.hivo.co/approvals/upload-approvals">https://support.hivo.co/approvals/upload-approvals</a></td></tr><tr><td><h3>Asset Approvals</h3></td><td>Asset Approval focuses on approving updated or edited versions of existing assets</td><td><a href="https://support.hivo.co/approvals/asset-approvals">https://support.hivo.co/approvals/asset-approvals</a></td></tr><tr><td><h3>Smart Compare</h3></td><td>Detect differences such as color, size, watermark changes.</td><td><a href="https://support.hivo.co/approvals/smart-compare">https://support.hivo.co/approvals/smart-compare</a></td></tr><tr><td><h3>Template Approvals</h3></td><td>Manages the approval process for templates before they are made available for use in the Editor (HIVO's editing tool)</td><td><a href="/approvals/template-approvals.md">Template Approvals</a></td></tr><tr><td><h3>Consent Approvals</h3></td><td>Manages the consent approval process, documenting and administering necessary legal documents or consents for image usage</td><td><a href="/approvals/consent-approvals.md">Consent Approvals</a></td></tr><tr><td><h3>People Approvals</h3></td><td>Review suggested people matches and quickly assign them to existing profiles or ignore incorrect matches</td><td><a href="/approvals/people-approvals.md">People Approvals</a></td></tr><tr><td><h3>Asset Readiness Report</h3></td><td>Manage readiness status of each asset, supporting accurate and timely approval decisions</td><td><a href="/approvals/asset-readiness-report.md">Asset Readiness Report</a></td></tr><tr><td><h3>Version Access Requests</h3></td><td>Manages and tracks access requests from lower-level users for different asset versions</td><td><a href="/approvals/version-access-requests.md">Version Access Requests</a></td></tr><tr><td><h3>Workflows</h3></td><td>Create &#x26; manage workflows to run a pre-defined approval process on your team</td><td><a href="https://support.hivo.co/approvals/approval-templates">https://support.hivo.co/approvals/approval-templates</a></td></tr></tbody></table>


---

# 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/approvals.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.