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

# Purchase approval setup

The Marketplace Platform allows you to set up approval workflows and approval groups depending on the price or publisher. An approval group represents a set of individuals who can approve orders. 

By creating workflows and approval groups, you can simplify the configuration and maintenance of the approval limits assigned to individual users. 

After creating groups, you can maintain them easily by linking approval groups together through parent-child relationships. Each approval group can only have one parent, but it can be used as a child in several approval groups.

See the following links to get started with purchase approval groups:

* [Create Approval Groups](/modules-and-features/procurement/purchase-approval-setup/create-approval-groups.md)
* [Create Approval Workflows](/modules-and-features/procurement/purchase-approval-setup/create-approval-workflows.md)
* [Delete Workflow Rules](/modules-and-features/procurement/purchase-approval-setup/delete-workflow-rules.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.platform.softwareone.com/modules-and-features/procurement/purchase-approval-setup.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.