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

# Create approval groups

Only administrators can create new approval groups. If another person wants to create workflows, either the administrator can enable access for that person, or the individual can contact their SoftwareOne Account Manager.

## Creating a new approval group

To create an approval group:

1. Navigate to **Procurement** > **Purchase Approval Setup**.
2. On the **Purchase Approval Setup** page, select **New Group**. 
3. In **Create Approval Group**, provide the following details:
   1. **Name** - Enter a name for the group.
   2. **Approval Level** - Choose an approval level from the list. You can create up to 3 levels of purchase approval groups.
   3. **Login(s)** - Select members that you want to add to the group. 
4. Select **Create**. The group is created, and a confirmation message is displayed. 


---

# 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-groups.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.