> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-7-compliance/editor/7.1-know-your-partner-kyp-documentation.md).
# 7.1 Know Your Partner (KYP) Documentation
* Each time a new affiliate/IB signs up, the platform depending on the Default Compliance Status (settled on[ Section 5, in Brand section](/track360/section-5-settings/editor/5.1-brand-management.md#affiliate-default-settings)) if is demanded will go directly to the KYP Pending Documentation
* The KYP Documentation section will be shown every time a new affiliate/IB sign up, depending on compliance status in the brand setting will be the application status
* Navigate by the **left Sidebar Menu** and click on the **Compliance > Pending KYP**
* Use the **Filter** on the upper bar to search:
* By specific **Affiliate**
* By **Application Status** of the affiliate’s documents
* By **Regulation Type**
* Determine the order of the list (newest to oldest or vice versa)
* After determining all filters, click on the **Search** button to apply the filters for the search
* Click on the selected row or use the **Actions menu** on the rightmost side of the desired affiliate to obtain more details:
* **User Information**
* Review the **uploaded documents**
* **Request for more documents** to the affiliate, if you want additional documents to be requested
* Upload a **Questionnaire**
* **Forced Approve Application or Reject Application**
---
# 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://track360.gitbook.io/track360/section-7-compliance/editor/7.1-know-your-partner-kyp-documentation.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.
