> 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-guides/customer-account/dashboard-overview/approvals.md).

# Approvals

Review and approve order and quote requests before purchases are finalized.

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

In organizations that require approval before purchases are finalized, order or quote 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 and quotes comply with internal approval processes before being placed.

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

<figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-21812cb7a61ec429b73dde748fe5ede09b7ddc05%2Fapproval_request.png?alt=media" alt="Checkout with option to request order approval"><figcaption><p>Checkout with option to request order approval</p></figcaption></figure>

Additionally, if they cannot accept an open quote on their own (based on their customer group and the company purchasing limit), they can also request approval from the quote details page by selecting **Inquire Approval**.

<figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-74917ebf69a4538d7c86b888b9d2b2b37e336e63%2Fquote_inquire_approval.png?alt=media" alt="Requesting quote approval"><figcaption><p>Requesting quote approval</p></figcaption></figure>

The pending orders and quotes are visible in the Approvals List.

<figure><img src="https://4011296124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOgeoK7nW6gEh0q1ceUZP%2Fuploads%2Fgit-blob-2442357bdb1637b3982ddb032cf912af812d6044%2Fquote_pending_approval.png?alt=media" alt="Carts and quotes pending approval"><figcaption><p>Carts and quotes pending approval</p></figcaption></figure>

{% hint style="info" %}
For related configuration and user management guidance, see:

* B2B Commerce Frontend: [User Management](/frontend-guides/customer-account/dashboard-overview/user-management.md)
* Management Dashboard:
  * [Customers](/user-guides/management-dashboard/customer-management/customers.md)
  * [Companies](/user-guides/management-dashboard/customer-management/companies.md)
  * [Groups](/user-guides/management-dashboard/customer-management/customer-groups.md)
  * [Quotes – Send for approval](/user-guides/management-dashboard/quotes/quotes-view.md#send-for-approval)
    {% endhint %}


---

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