> 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/purchase/purchase-module/masters/po-type-user.md).
# PO Type User
The **PO Type User** feature is used to assign applicable Purchase Order (PO) Types to users based on their department. It also allows users to perform bulk PO updates when bulk selection is enabled.
## Steps to View and Configure PO Type User
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. In the **Purchase** menu, click on **Masters**.
2. Select **PO Type User** from the sub-menu.
* The PO Type User screen will appear.
Step 2: Click on the **Open** button.
Step 3: Select the required **User** from the available list.
1. Select the appropriate **Department**.
* These settings define the department-wise Purchase Order access for the selected user.
Step 4: Enable the **Bulk Selection** option.
* This allows users to update multiple Purchase Orders in bulk.
Step 5: Select the required **Applicable PO Type** from the available options.
Step 6: Click on the **Save** button.
* The PO Type User configuration will be saved successfully.
---
# 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/purchase/purchase-module/masters/po-type-user.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.
