> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/practical-guides/create-an-approval-process.md).

# Create an approval process

Creating and managing task workflows within Jet Admin

Require a person to approve an action before it executes. This guide covers the button approval and task queue controls shown in the existing builder walkthroughs.

The walkthrough uses a refund request. Use fictional data and a test action when learning the process.

{% embed url="<https://youtu.be/BjmAml_w0Fs>" %}

## Before you start

Define the action requiring approval, the person who should review it, and the details they need. Confirm that the intended requester and approver can access the relevant app and queue. A queue assignee and the underlying data-source permissions are separate concerns.

## Enable approval on the button

1. Select the button.
2. Open its **Actions** tab.
3. Enable approval for the button's action.

{% @arcade/embed url="<https://app.arcade.software/share/W7yFruiDSvPP52U30AS4>" flowId="W7yFruiDSvPP52U30AS4" %}

## Create a task queue

1. Choose **Select a Queue**, then **Add New**.
2. Name the queue.
3. Define statuses for the stages and outcomes.
4. Save the queue.

{% @arcade/embed url="<https://app.arcade.software/share/qmB5ddpxXbdoBGggMKAP>" flowId="qmB5ddpxXbdoBGggMKAP" %}

Configure parameters that will help the approver understand the request, such as ticket ID, transaction ID, amount, and reason.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-Mjh15jd2ixodHPddB36%2F-Mjh2lJMVq3y4EMAHPj4%2Fimage.png?alt=media\&token=80599065-f37b-42a5-8980-9fc2e320382a)

## Configure the approval task

Select the queue, then configure:

* **Task Name:** a fixed name or a formula containing request details.
* **Initial status:** the state before the decision.
* **Initial assignee:** the person who should review the request.
* **Status after approval:** the queue state after approval.
* **Status after reject:** the queue state after rejection.

Choose status labels that match your process. A status label describes the task; it does not replace the approval decision.

{% @arcade/embed url="<https://app.arcade.software/share/EFRLLMuftK6UfHCHNAE5>" flowId="EFRLLMuftK6UfHCHNAE5" %}

Map the task parameters to values from the app.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-Mjh15jd2ixodHPddB36%2F-Mjh46JHrLZuRF9KhGzI%2Fimage.png?alt=media\&token=3c756c64-222e-4e4b-99e6-8049ffed513b)

## Review and decide

Run the button action with fictional data to create a request. Open the collaboration/task queue interface as the intended approver.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MO5c8r8iHD0iy25YmfD%2F-MO5fTqxXSpk87kxahBQ%2F%D0%91%D0%B5%D0%B7%D1%8B%D0%BC%D1%8F%D0%BD%D0%BD%D1%8B%D0%B9.png?alt=media\&token=c06a8397-01d8-4d34-b912-3f69abe2f196)

Use the queue filters to find the request by assignee, date, or priority.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MO5c8r8iHD0iy25YmfD%2F-MO5g4p9axBF4_VvC2av%2FGIF157.gif?alt=media\&token=e73ab5f7-1674-42a1-988e-3bf8ccdb254d)

Open it and inspect the details passed from the app.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MO5c8r8iHD0iy25YmfD%2F-MO5h4bfA6f-jK0RUktn%2FGIF159.gif?alt=media\&token=0fc19f6c-caf9-4dae-b2f7-1cfb9344a103)

Approve to execute the configured action and update the task status, or reject to update the task status without executing that action.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MO5c8r8iHD0iy25YmfD%2F-MO5gk6yPpmI3QSMnfqB%2FGIF158.gif?alt=media\&token=f4799030-f6e5-4c83-937b-1bdcfebe6140)

## Test both outcomes

Create separate test requests for approval and rejection. Confirm that approval executes the intended action once and rejection leaves the target data unchanged.

Also test with the intended requester and approver accounts. If a request exists but the action fails after approval, inspect the operation's permissions and input rather than treating the queue status alone as proof of success.

See [testing](/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.md) and [failure handling](/workflow/handle-outcomes/handle-failures-and-prevent-duplicate-processing.md).


---

# 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.jetadmin.io/workflow/practical-guides/create-an-approval-process.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.