> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/flagship-deprecated/navigating-the-interface/archiving-use-cases-from-the-dashboard.md).

# Archiving use cases from the dashboard

## 📖 Definition

**Archiving** a use case enables you to get rid of obsolete use cases and keep your dashboard **clean** and **up-to-date** by viewing only the projects and use cases that you are currently working on.

## ⚙️ Configuration

This action can be performed by users with a User, Admin or Super admin role.\
To archive a use case, apply the following steps:

1. Hover over the use case you want to archive and click the 3 dots.
2. Click *Archive*.
3. Select the folder you want to move the use case to. If no folders are created, click *New folder*.
4. Click *Archive*:\
   Your use case is archived.

| <p>⭐ Good to know</p><p>You can’t unarchive a use case. If you want to push it live again, we recommend duplicating it.</p> |
| --------------------------------------------------------------------------------------------------------------------------- |

Once a use case is archived, you can access it from the **Archived** tab of the dashboard.\
From there, you can organise your use cases by folders (instead of projects for the non-archived ones). This enables you to better organize your use cases once they are archived. For instance, you can store outperforming experiments in the same folder.\
You can still access the reporting of your archived use cases until the legal timeframe specified in your package.

![Archived\_use\_cases.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-3b5ad6d6a65d5a10f14e205b9d663be8ce123bfd%2F646dd9eee4fae0d6874cbc37f5f2b4b1.png?alt=media)

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# 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://docs.abtasty.com/flagship-deprecated/navigating-the-interface/archiving-use-cases-from-the-dashboard.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.