> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/procurement/purchase-approval-setup/create-approval-workflows.md).

# Create approval workflows

Only administrators can create new approval workflows. 

## Creating a new approval workflow

To create an approval workflow:

1. Navigate to **Procurement**  > **Purchase Approval Setup**. 
2. In the **Actions** column, select **Approval Workflow Setup**.
3. In the **Approval Workflow Setup** window, do the following: 
   * **Purchase Approval Group** - Select a group that will approve the user’s transaction when approval is required.
   * **Currency** - Select the currency on which the rule will apply. Selecting **Any** applies the rule to all currencies.
   * **Publisher** -  Select a publisher if you want to create a workflow role for a specific publisher. If you select **Any**, the workflow rules apply to all publishers.
   * **Total Amount** - Specify the maximum allowable spend limit for an individual transaction without the need for approval. Transactions exceeding this limit must be reviewed and approved by the designated Purchase Approval Group.
4. Select **Create Rule**.
5. Select **Save**.


---

# 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.platform.softwareone.com/modules-and-features/procurement/purchase-approval-setup/create-approval-workflows.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.