> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/user-journeys/partner-journey.md).

# Partner Journey

Follow a Partner (Broker) from logging in to submitting a deal and requesting documents.

A Partner (Broker) submits deals for customers through the partner portal.

{% stepper %}
{% step %}

#### Log in

Partners log in to the partner portal.
{% endstep %}

{% step %}

#### Track deals

The partner portal shows a "Deal Pipeline".
{% endstep %}

{% step %}

#### Start a deal

The Partner starts a deal for a customer.
{% endstep %}

{% step %}

#### Request documents

The Partner can email the customer a document request link. It opens a no-login page where the customer uploads the requested documents.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
A product's **Sub-category** is **Broker** or **Borrower**. It decides whether the product shows in the applicant portal or the partner portal. See [Product Classification](broken://pages/iXWUGrvKWYOJg6yzNcaC) and [Decide the Product Type](broken://pages/pUWg5cwsueJfptR9K75P).
{% endhint %}

<table data-view="cards"><thead><tr><th>Related</th><th data-card-target data-type="content-ref">Page</th></tr></thead><tbody><tr><td>The customer side, including the document request link.</td><td><a href="/retail-lending/user-journeys/applicant-journey.md">Applicant Journey</a></td></tr><tr><td>What FI staff do with a submitted application.</td><td><a href="/retail-lending/user-journeys/fi-staff-journey.md">FI Staff Journey</a></td></tr><tr><td>All journeys side by side.</td><td><a href="/retail-lending/user-journeys.md">User Journeys</a></td></tr></tbody></table>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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://docs.uptiq.ai/retail-lending/user-journeys/partner-journey.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.