> 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/review-partner-applications.md).

# パートナー申請を確認する

- [却下された申請者を Advocate にリダイレクトする](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/redirect-rejected-applicants-to-advocate.md)
- [リクルートメントエージェント](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/recruitment-agent.md)
- [効果的なエージェント指示を書く](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/recruitment-agent/write-effective-agent-instructions.md)
- [リクルートメントエージェントの結果を追跡する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/recruitment-agent/track-recruitment-agent-results.md)
- [リクルートメントエージェントを設定する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/recruitment-agent/set-up-the-recruitment-agent.md)
- [パートナー申請処理を自動化する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing.md)
- [パートナー申請を自動処理するワークフローを作成する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md)
- [ワークフローの却下メッセージを設定する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-up-a-workflows-reject-message.md)
- [ワークフローのベストプラクティスと FAQ](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/workflow-best-practices-and-faqs.md)
- [リクルートメントワークフローの説明](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/recruitment-workflows-explained.md)
- [申請ワークフローの実行順序を設定する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.md)
- [パートナーおよびクリエイターの申請を確認する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/review-partner-and-creator-applications.md)
- [申請を管理して提案を送信する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals.md)
- [パートナーを一括処理し、却下を取り消す](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/process-partners-in-bulk-and-reverse-rejections.md)
- [事前承認済みパートナー申請リストを管理する](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-your-pre-approved-partner-application-list.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/review-partner-applications.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.