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

# Approvers

There can be multiple people in the organization who need to approve a quote depending what's in the quote. For example, a deal with a very large discount might require approval from the Chief Revenue Officer or the Chief Financial Officer. Or if the quote contains a product that's in early access, Product Management may have to weigh in.

Since people change roles in a company, Bunny lets you define abstract approvers to avoid having to update  rules when people join, leave or move around in the organization.

<figure><img src="/files/jwLnGiqZ5S2gbs3sungQ" alt=""><figcaption><p>Approvers</p></figcaption></figure>

For now, an approver is simple a Bunny user, but this will change as we evolve the concept.


---

# 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/approvers.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.
