> 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/point-of-sale/point-of-sale-module/masters-3/user-privilege.md).
# User Privilege
The **User Privilege** feature is used to assign permissions and access rights to users in the system. It helps control which modules, functions, and operations a user can access based on their role and responsibilities.
### Steps to Open and Configure User Privileges
Step 1: Navigate to the **Point of Sale** module.
1. Go to **Master3 > User Privilege**.
* The User Privilege screen will appear.
Step 2: Click on the **Open** button to proceed.
Step 3: Select the required user to whom privileges need to be assigned.
* Ensure the correct user is selected before assigning permissions.
Step 4: Select the required **User Privileges** from the available options.
* Enable or disable permissions based on the user’s role and access requirements.
* Review the selected privileges carefully before saving.
Step 5: Save the User Privileges
* After selecting the required privileges, click on the **Save** button to successfully save the user permissions.
---
# 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/point-of-sale/point-of-sale-module/masters-3/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.
