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

# テンプレート条件のパートナーを確認

パートナーの現在のステータス（提案や申請を含む）を追跡し、ブランドとの契約履歴全体を確認することで、パートナーの有効・保留中・期限切れの契約条件を確認および管理できます。

#### テンプレート契約条件に追加されたパートナーを表示する

1. 左側のナビゲーションメニューから、 ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **契約 → テンプレート契約条件**.
2. 表示するテンプレート契約条件を見つけます。
3. このテンプレート契約条件の有効なパートナーを確認するには、次を選択します。 **リンクされた数字** 「 *有効* 」列の下にある項目。

パートナーの契約履歴を表示する方法について詳しくは、次を参照してください。 [パートナーの契約履歴を表示する](https://help.impact.com/brand/ja/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/ja/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.
