> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/cpq/quote-approvals.md).

# Approvals

Route quotes through an internal approval process before they reach the customer.

Many teams need a quote to be approved internally — by a manager, or by finance when a discount exceeds a threshold — before it is sent to the customer.

{% hint style="warning" %}
Approval flows are custom work. Limio does not ship a pre-built approval process; the steps below describe how to build one on standard Salesforce functionality.
{% endhint %}

## Using standard Salesforce approvals

`Limio_Quote__c` is a custom object, so it supports Salesforce's standard **Submit for Approval** action like any other object.

The packaged Limio Quote record page already has the **Submit for Approval** action.

1. Define your approval process for the Limio Quote object in **Setup**, under **Approval Processes**. The **Submit for Approval** action starts only this type of process. A flow approval process needs a custom button. See the [Salesforce documentation](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_deploy_add_button_to_record_page.htm\&language=en_US\&type=5).
2. In the process, set the field **Approval Status** to Pending when the rep submits the quote.
3. Set **Approval Status** to Approved or Rejected when the process ends.
4. For quotes that do not need approval, set **Approval Status** to Not Required.
5. Optionally, move the quote to **In Review** on submission and **Approved** on approval. See [Quote Statuses and Lifecycle](https://docs.limio.com/salesforce/cpq/quote-statuses.md).

{% hint style="info" %}
**Approval Status** is Needed on a new quote. The record page shows **Send Quote By Email** only when **Approval Status** is Approved or Not Required. Until a process or a user changes the value, the action does not show.
{% endhint %}

The packaged permission sets give read-only access to **Approval Status**. Thus, set the value from your approval process or from a record-triggered flow. To let users change the value, give edit access to the field in your own permission set.

**Edit Limio Quote** does not change **Approval Status**. Thus, an approved quote stays Approved after an edit. To get a new approval after an edit, reset **Approval Status** in your own automation.

## Fields useful as approval criteria

The Limio Quote record carries the values most approval rules key off:

<table><thead><tr><th width="270">Field</th><th>Use in approval criteria</th></tr></thead><tbody><tr><td><code>Discount_Percent__c</code></td><td>Require approval above a discount threshold</td></tr><tr><td><code>Discount_Amount__c</code></td><td>Require approval above an absolute discount value</td></tr><tr><td><code>Amount__c</code></td><td>Require approval above a deal size</td></tr><tr><td><code>Has_Manual_Price_Override__c</code></td><td>Require approval whenever a rep has overridden a price. The package does not set this field. Map the output <strong>Contains Manual Price Overrides</strong> of <strong>Limio Cart Items</strong> to it in your override of the Upsert Limio Quote flow. <strong>Limio Subscription Change Items</strong> has no price override and no such output. Thus, on a quote that updates a subscription, the field stays false. <strong>Assisted Sales - User</strong> gives read-only access to this field. Thus, give your reps edit access in your own permission set.</td></tr><tr><td><code>Quote_Totals_JSON__c</code></td><td>Detailed totals, discounts, taxes and line items from the billing preview</td></tr></tbody></table>

See the [object definition](https://docs.limio.com/salesforce/cpq/quote-object-definition.md) for the full field reference.

## Gating the checkout link on approval

If links should only reach the customer once a quote is approved, generate them from your approval flow rather than letting reps generate them from the UI:

{% content-ref url="/pages/weUK9k5qRel3RKZDvnla" %}
[Links from Apex](https://docs.limio.com/salesforce/cpq/generate-links-from-apex.md)
{% endcontent-ref %}

{% hint style="warning" %}
An order can need to wait for approval, or an approval process can lock the quote. In these cases, remove the choice `Submit_Order_choice` from the field `Select_quote_action` in your override of the **Generate Checkout Link from Limio Quote** flow. Keep the field, because it also holds the preview and checkout choices. From v14.44, the quote record page has [Submit Order](https://docs.limio.com/salesforce/cpq/submit-order.md), and Submit Order ignores the approval status of the quote. On a locked quote, Submit Order takes the payment, but it cannot update the quote. Then Submit Order shows again for the next rep.
{% 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://docs.limio.com/salesforce/cpq/quote-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.
