> 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-1/table-groups.md).
# Table Groups
The **Table Groups** screen is used to assign and manage table groups for a selected outlet in the system.\
Using this screen, users can select an outlet and define which table groups are active for that outlet.
## Steps to Open Table Groups
Step 1: Navigate to the **Point of Sale** module and select **Masters1**.
1. Click on **Table Groups**.
* The Table Groups screen will open.
Step 2: In the Table Groups screen, click on the **Open** button.
* The configuration window will appear.
Step 3: Locate the **Outlet** field.
1. Select the required outlet from the available list.
* The selected outlet will be used to configure table groups.
* Ensure the correct outlet is selected before proceeding.
Step 4: After selecting the outlet, locate the **Active Table Group** section.
1. Select the required table group(s) from the available options.
* These selected table groups will be activated for the chosen outlet.
* Verify all selections carefully before saving.
Step 5: After completing all selections, click on the **Save** button.
* The table group configuration will be successfully saved in the system.
---
# 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-1/table-groups.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.
