> 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-transactions/mm-transactions-material-request-approval.md).
# Material Request Approval
Steps to perform material request approval
The **Material Request Approval** process allows authorised personnel, such as Department Heads, to review and approve Material Requests submitted by users. Approval is required before the requested materials can be processed and issued from the store. This process helps ensure that all material requests are authorised and comply with departmental requirements.
## Steps to Perform Material Request Approval
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **Material Request Approval**.
* The Material Request Approval screen will be displayed.
Step 2: From the list of pending requests, select the Material Request that requires approval.
1. Ensure that the correct request has been selected before proceeding.
Step 3: Click the **Approve** button.
* Once approved, the Material Request will be available for further processing and material issuance.
---
# 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-transactions/mm-transactions-material-request-approval.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.
