> 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/banquet/banquet-module/masters/aids.md).
# Aids
The **Aids** master in the Banquet Module is used to create and manage Aids details. This section allows users to add new Aids records by entering important information such as Aids ID, Aids Name, Aids Group, and Department Name.
## Steps to Create a Aids Master
Step 1: Login to the application and navigate to the **Banquet Module**.
1. Click on **Masters**.
2. Select **Aids** from the Masters menu.
* After selecting the Aids option, the **Aids Details** screen will be displayed.
Step 2: Click on the **Open** button
1. The screen displays the list of already created Aids.
2. You can review the existing records and their details.
Step 3: Click on the **New** button.
1. Enter the required details in the respective fields:
* **Aids ID** – Enter the unique ID for the Aid.
* **Aids Name** – Enter the name of the Aid.
* **Aids Group List** – Select the appropriate Aid Group from the list.
* **Department Name** – Select the related department name.
2. Verify that all the entered details are correct.
Step 4: After entering all the required information, click on the **Save** button.
1. The Aid details 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/banquet/banquet-module/masters/aids.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.
