> 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/approvals.md). # Approvals Assets can be set to require approval from Users with the ‘Can Approve’ Regular User permission. Asset approvals will be stored under the ‘Approvals’ section (thumbs up icon in the left nav bar) instead of the Library whilst they are pending. This is particularly useful for when you want to manage non-staff users (e.g. freelancers) who have uploading permissions.

Clicking one of the batches will show all Assets in that batch, including all fields that were filled out during the uploading process (and can be modified here). Click ‘Approve Asset’ or ‘Reject Asset’ to continue. Rejecting an Asset will delete it from HIVO. To make Assets require Approvals, Admins can toggle on the ‘New Assets are added to Upload Approvals’ option inside Client Profile => Settings => Upload/Download Settings. Version approval of Assets can be requested/accepted in the Asset’s Detail page under the ‘Approval’ thumbs up icon. A Version is still accessible while it’s awaiting approval, and is used for internal approvals (e.g. checking if a report is OK to send out).

In the uploader’s ‘Asset Details’ step, Admin users will be able to tick the ‘Skip Approval Step for Uploads’ option under ‘Automations’. New Assets will otherwise always require approval if the required Approvals setting has been turned on. --- # 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/~/changes/eaCuYFhybbREuBouwZp6/approvals.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.