> 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/general-ledger/general-ledger-module/gl-masters/voucher-type-user-privilege.md).
# Voucher Type User Privilege
**Voucher Type User Privilege** is used to define and manage user access rights for specific voucher types within the accounting system. These privileges determine which users are authorised to create, view, edit, approve, or delete accounting vouchers.
## Steps to Configure Voucher Type User Privileges
Step 1: Navigate to the **General Ledger** module.
1. Click **Masters 1** from the menu.
2. Select **Voucher Type User Privilege** from the list.
* The Voucher Type User Privilege screen will be displayed.
Step 2: Click the **Open** button.
1. Select the required user from the list.
* Once the user is selected, the privilege configuration screen will appear.
Step 3: The system will display the available voucher types and corresponding access permissions for the selected user.
* Enable the required privileges based on the user's role and responsibilities.
* Disable any privileges that should not be granted.
Step 4: After assigning the required privileges, click the **Save** button.
* The system will save the privilege settings for the selected user.
---
# 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/general-ledger/general-ledger-module/gl-masters/voucher-type-user-privilege.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.
