> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-masters/mm-masters-approval-settings.md).
# Approval Settings
Steps to set approval settings
**Approval Settings** are used to define the approval hierarchy and approval procedures for various transactions within the system. These settings determine how transactions are reviewed and approved before they are processed or finalised.
## Steps to Configure Approval Settings
Step 1: Navigate to **Master** menu in the **Inventory** module**.**
1. Click on **Approval Settings**.
* The Approval Settings screen will be displayed.
Step 2: After opening the Approval Settings screen, select the required **Transaction**.
Step 3: Select the appropriate **Store Type** from the available options.
Step 4: Define the required **Approval Levels**.
1. Select the applicable **Approval Procedure**.
Step 5: After configuring all approval levels and procedures, review the settings carefully.
1. Click the **Save** button.
* The Approval Settings will be saved successfully and applied to the selected transaction and store type.
---
# 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://help.rbsgo.com/material-management/material-management-module/mm-masters/mm-masters-approval-settings.md?ask=&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.
