> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/approval-workflows/how-approvals-work.md).

# How approvals work

When you build a quote, Bunny will continuously check if the quote triggers any approval rules. When that happens, the affected rules are shown in the sidebar along with a list of the approvers.

<figure><img src="/files/yihPLLe3AoOuNZhWui72" alt=""><figcaption><p>Quote with approval reasons</p></figcaption></figure>

A quote that requires approval cannot be shared with a customer and must first complete the approval process, which is kicked off using the **Start approval** link in the sidebar. During the approval process, the quote cannot be modified.

Bunny uses [workflows](/guide/tour/workflows.md) to drive the approval process via email and you can customize the email messages as well as add other interactions, such as Slack messages.

### Reviewing a quote

When an approver clicks the **review quote** link in the email, a read-only version of the quote is shown. When viewed on a mobile device, the layout will be more compact, but still readable.

<figure><img src="/files/QyNxdr5Ja8f6SWGoTM8H" alt=""><figcaption><p>Quote approval</p></figcaption></figure>

The approval page shows a summary of the quote as well as all the line items. Basically the same view as the quote editor. The reasons for the approval request and the chain of approvals are shown in the sidebar.

### Rejecting a quote

<figure><img src="/files/dU7WuCZwBW9njpoMz3Gx" alt=""><figcaption><p>Quote rejection</p></figcaption></figure>

The approval process continues until an approver rejects the quote. A reason can be provided along with the rejection and the deal owner will receive an email with the reason.


---

# 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.bunny.com/guide/tour/approval-workflows/how-approvals-work.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.