> 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/fr/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/review-partners-on-template-terms.md).

# Examiner les partenaires sur les conditions de modèle

Vous pouvez examiner et gérer les conditions actives, en attente ou expirées de vos partenaires en suivant leur statut actuel, notamment les propositions et les candidatures, et en consultant l’historique complet des contrats conclus entre le partenaire et votre marque.

#### Afficher les partenaires ajoutés à des conditions modèles

1. Dans le menu de navigation de gauche, sélectionnez ![](https://57104473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **Contrats → Conditions modèles**.
2. Recherchez les conditions modèles que vous souhaitez afficher.
3. Pour voir les partenaires actifs associés à ces conditions modèles, sélectionnez **le nombre cliquable** dans la colonne *Actifs* .

Pour en savoir plus sur la consultation de l’historique des contrats d’un partenaire, consultez [Afficher l’historique des contrats d’un partenaire](https://help.impact.com/brand/fr/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/view-partner-contract-history.md).


---

# 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/fr/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/review-partners-on-template-terms.md?ask=<question>&goal=<user_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.
