> 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/approval-rules.md).

# Approval rules

Approval rules are what trigger approval workflows. As a sales rep builds a quote, Bunny checks if the quote triggers any approval rules. This happens every time the quote is updated in the UI.

<figure><img src="/files/rHLKDiB49Ut88UiNkpGN" alt=""><figcaption><p>Approval rule</p></figcaption></figure>

### Approval rule name

This should be something very succinct is it will be showed in the sidebar on the quote building as well as on mobile screens when approvers look at quotes.

### From and to date

These two fields help with temporary or time-dependent rules.

### Active

Easily disable a rule that's not needed for a while.

### Approver

This approver will be notified when this rule is triggered.

### Conditions

Approval rules can have the following conditions and are triggered when *all* the conditions are met:

* Overall quote amount is greater than X
* Overall quote discount is greater than X
* Any line item diocount is greater than X
* Product X is included in the quote
* Plan X is cinluded in the quote
* A billing period is monthly/quarterly/semi-annual/annual

If you are looking for additional rules, let us know how we can help.


---

# 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/approval-rules.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.