> 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/platform-features/contracts-and-template-terms/contracts/view-partner-contract-history.md).
# View Partner Contract History
You can check your contract history for each of your partners. This is helpful when you need to audit your partnership history with that partner, troubleshoot any issues, or resolve any payment misunderstandings.
#### View a partner's contract history
You can view the contract history for each of your partners.
1. From the left navigation bar, select  **\[Engage]** → **Partners → Partners**.
2. Hover over the partner for which you want to check their contract history, then select  **\[More] → Contract → View History**.
3. From here, you have a few options:
* You can view the status, start and end dates, and the brand and partner signatories for each generation of your partnership.
* To view the exact terms for each generation of contracts, hover over the partner contract, then select  **\[More]** → **View**.
#### View all contract histories
You can also view all of your contracts' histories. This is where you can search by the signatory, the template term associated with the contract, what partners accepted that contract, and what state the contracts are in.
1. From the left navigation bar, select  **\[Engage]** → **Contracts → Contracts**.
2. From here, you can view all contract histories, or filter your search.
* Refer to the *filter reference* for more information.
Filter reference
| Filter | Description |
| ------------- | ---------------------------------------------------------------------------------------------------- |
| **Signatory** | Enter the name of the brand or partner signatory associated with the contract you are searching for. |
| **Template** | From the drop-down menu, select the template term(s) for the contract(s) you are searching for. |
| **Partner** | From the drop-down menu, select the partner(s) that agreed to the contract(s) you are searching for. |
**State**
From the drop-down menu, select what contract state the contract you are searching for is in.
**States reference**
| Filter | Description |
| ------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Pending | View all the partners with whom you have yet to accept contract terms. |
| Active | View partners that you are currently working with and have approved. |
| Upcoming | View partners that you will soon be working with. |
| Rejected | View partners that you have declined. |
| Expired | View partners whose contract or work agreement terms have come to an end. |
| Suspended | View partners that you've stopped working with but might reinstate in the future. |
| Expired (Non-Compliant) | View partners that you no longer work with past a certain date due to being non-compliant with your terms. |
| Suspended (Non-Compliant) | View partners you no longer work with due to being non-compliant with your terms. |
---
# 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/platform-features/contracts-and-template-terms/contracts/view-partner-contract-history.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.
