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

# Archiving Assets

Assets can be Archived if you want to restrict their visibility to only users with the ‘Can View Archived’ permission and prevent them from being shared.

Archived assets won’t appear in normal search results, unless the ‘Archived’ search filter is on (click the down arrow on the Library search bar to open filter options). Archiving can be useful for managing old Assets that you still want to retain access to. When an Asset is Archived, it will no longer appear within Shared Links.

When Archiving Assets, a date can be set for when the Archive status is applied from. Archiving can be done on multiple Assets at once through[ Library Actions](/~/changes/eaCuYFhybbREuBouwZp6/library/library-actions.md), or on the Asset Detail page by clicking the ‘permissions’ gear icon => Archive Date. Use the Archive Date ‘now’ option to instantly Archive the Asset. To unarchive Assets, follow the same steps as archiving them but set the archive date to be empty by hitting backspace on each of the date fields (i.e. so that it’s left a value of dd/mm/yyyy).

Assets can also have the Archive Date marked on upload in the ‘Asset Details’ step.

In the Client Profile => settings tab => archive settings, you can set client wide default Archive dates and options to notify Admins when Assets are archived.


---

# 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/assets/archiving-assets.md?ask=<question>&goal=<endgoal>
```

`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.