> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/frontend/customer-account/dashboard-overview/approvals.md).

# Approvals

The **Approvals** section supports internal purchasing workflows common in B2B environments.

In organizations that require approval before orders are finalized, purchase requests submitted by users appear in this section. Designated approvers can review the request details, including products, quantities, and order totals, and then approve or reject the request according to company policies.

This feature helps organizations maintain purchasing control and ensures that orders comply with internal approval processes before being placed.

When a customer places an order that exceeds the approved limit, they can request an approval for it during the checkout process.

<figure><img src="/files/0hQIsjDubBgrIaaJpChy" alt=""><figcaption><p>Checkout with option to request order approval</p></figcaption></figure>

Then, the pending order is visible in the Approvals List.

<figure><img src="/files/rEWI7owL388NPoIcgaCY" alt=""><figcaption><p>Approvals list</p></figcaption></figure>


---

# 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://developer.emporix.io/frontend/customer-account/dashboard-overview/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.