> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/archive-partners.md).
# Archive Partners
Sometimes, prospects don't work out. When this happens, archive these prospects to prevent them from clogging up your *Prospects* screen. You have 2 ways to archive prospects:
* Archive a prospect from the *Prospects* screen.
* Archive a prospect when viewing their profile.
#### Archive a prospect from the Prospects screen
You don't need to view the prospect's profile to archive them.
1. From the left navigation menu, select .svg?alt=media\&token=8a0e56eb-ff89-4046-8e72-ad2b503f8bf9) **\[Discover]** → **Prospects**.
2. From the *Prospects* screen, find the prospect you want to archive.
3. Hover over their line in the table. At the right end of the line, select  **\[More]** → **Archive**.
4. Read the warning message, then select **Archive**.
#### Archive a prospect from the prospect's profile
You can archive the prospect when you're reviewing their partner profile.
1. From the left navigation menu, select .svg?alt=media\&token=8a0e56eb-ff89-4046-8e72-ad2b503f8bf9) **\[Discover]** → **Prospects**.
2. From the *Prospects* screen, find the prospect whose profile you want to view.
3. Select their row in the table. Their profile will appear.
4. Review their profile as needed.
5. Select  **\[Archive**].
6. Read the warning message, then select **Archive**.
#### View archived prospects
1. From the *Prospects* screen, navigate to the filter menu.
2. Change the *Show* filter to **Show Archived** to include them in the table.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/archive-partners.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.
.png?alt=media&token=869eb1d9-271a-402c-ac59-fd681f505cdd)