> 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/masters/main-master-module/privileges/module-user-privilege.md).
# Module User Privilege
**Module User Privilege** is used to control and manage what a user can do inside different system modules. It defines permissions such as viewing, creating, editing, approving, or deleting records. This ensures proper security, role-based access, and segregation of duties within the system.
## Steps to Assign Module User Privileges
Step 1: Go to the **Main Menu** of the application and click on **Settings**.
1. Under the Settings menu, click on **Privileges**.
2. From the available options, select **Module User Privilege**.
Step 2: Click on the **Open** button. 
Step 3: Choose the required **Company Name** from the list.
Step 4: Select the **User** for whom the privileges need to be assigned.
1. After selecting the user, the system will display available modules and their permission options.
Step 5: After assigning the required permissions, click on the **Save** button.
* The system will store the assigned module privileges 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/masters/main-master-module/privileges/module-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.
.png?alt=media)
