> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/projects/archive-and-unarchive-projects.md). # Archive and Unarchive Projects Feature to better manage and visualize projects Archiving projects on the Currents Dashboard allows you to temporarily set aside projects while retaining access to essential data and test results associated with those projects. On the organization's main page on Currents Dashboard, you can view and manage all the projects associated with your organization. This feature is crucial when you need to manage a large number of projects within your organization, some of which may not be actively in use for a while. {% embed url="" %} Archiving and unarchiving projects {% endembed %} Archiving and unarchiving projects is a way to keep your workspace organized and decluttered by moving less active projects out of sight while still being able to access and work on them when necessary. It ensures you can focus on what's currently in progress and easily find and manage older or less active projects when needed. --- # 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://docs.currents.dev/dashboard/projects/archive-and-unarchive-projects.md?ask=&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.