> For the complete documentation index, see [llms.txt](https://docs.qiro.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qiro.fi/qiro-marketplace-product-guide/for-pool-admins/tokenization-approvals.md).

# Tokenization Approvals

#### **Minting Approvals for Borrowers**

Allows the Pool Admin to authorize a borrower to mint the tokenized asset (e.g., pool notes, tranche tokens, deal tokens).\
This approval is required before any minting transaction can occur and confirms that all compliance checks, documentation, and operational prerequisites have been satisfied.\
Once approved, the borrower can proceed to mint the asset that will be offered to investors.

#### **Underwriting Approvals for Borrowers**

Enables the Pool Admin to approve the borrower’s underwriting status based on credit evaluation, risk assessment, and internal scoring models.\
This action ensures the borrower’s deal structure meets the platform’s underwriting standards.\
Only after this approval can the deal move forward to the minting stage or investor onboarding.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qiro.fi/qiro-marketplace-product-guide/for-pool-admins/tokenization-approvals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
