> 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/tasks/task-actions/archiving-tasks.md).

# Archiving Tasks

Archiving a task can be useful when you don't want to delete the Task and its information but also don't want to clutter the task search process. Tasks can be archived so they no longer appear in Tasks search results.

{% hint style="info" %}
Note that you can still find archived tasks if you enable the **'Archived' search filter**.
{% endhint %}

## Archive Each Task (do the same with Unarchive)

* Open the task details you want to archive.
* Click the '**Archive**' button located in the lower right corner of the task details window.

<figure><img src="/files/Yp6vOKSlen66sJc77Ypr" alt=""><figcaption><p>Archive each Task</p></figcaption></figure>

## Storing Multiple Tasks

* In the Task list view, click the check box to the left of the task name to select task (you can select one or multiple or all tasks).
* Click the 'Actions' button and select 'Archive' from the menu.

<figure><img src="/files/Gq4nc33wFnQKeB2wlxsa" alt=""><figcaption><p>Storing multiple task</p></figcaption></figure>


---

# 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/tasks/task-actions/archiving-tasks.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.