> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/administration/pipelines/approval.md).

# Approval

An approval task enables you to get the approval of an app owner or app administrator before the pipeline will continue executing. In general this task should be placed first in the pipeline, however you can place it anywhere that you require an approval. The pipeline will pause execution until the required approvals have been received. The following options are available:

* **Approvers:** Select who is required to approve the release. When the pipeline executes the approvers will be sent an e-mail to notify them that a release is waiting for their approval.
* **Notification frequency:** How often (in days) that the approvers will be notified that the release is waiting for approval.


---

# 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.bluestorm.io/administration/pipelines/approval.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.