> 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/menu-privilege.md).
# Menu Privilege
Module–Menu Privilege is used to control user access within the system. It allows administrators to define what modules, menus, and actions a user can access based on their role. This helps ensure system security, proper authorisation, and controlled access to functionalities.
## Steps to Configure Module–Menu Privileges
Step 1: Go to the **Settings** menu in the system.
1. Click **Privilege,** then select **Menu Privilege.**
* The Menu Privilege screen will open.
Step 2: First, select the **Module** from the available list.
1. Next, select the **User** to whom you want to assign access rights.
2. After selection, the system will display the available **module rights and permissions** for that user.
Step 3: After selecting the module and user, click on **Menu Privilege**.
1. A new screen will appear showing the list of menus and available permissions.
2. Here, you can define what menus and actions the selected user is allowed to access.
Step 4: If you want to copy privileges from an existing user, click on **Replicate User Privilege**.
1. The replication screen will be displayed.
2. Select the **User (Source User)** whose privileges you want to copy.
3. Then select the **Module** for which privileges should be replicated.
* The system will display the selected user’s existing privileges for that module.
Step 5: Review the replicated or selected privileges carefully.
1. Modify permissions if required based on the new user’s access needs.
2. Ensure all required menu rights are correctly assigned.
Step 6: Once all privileges are finalised, click the **Save** button.
---
# 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/menu-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)
