> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/group-configuration.md).
# Group Configuration
When an existing group is selected or a new group is created in the Groups and Keys screen, its properties open on the Configuration tab.
Click the Delete button to remove this group and all the buttons it contains.
Click the Save button to save changes and exit.
Click the Exit button to close this window without saving changes.
#### Description
Type a meaningful name for this group.
#### Second Name
Type an alternate name for this group. On multi-language setup, this could be the direct translation of the description.
#### Background color
Select the background color to use. The option By default will use the default color of the selected workstation theme. Other colors can be selected from the drop-down list.
#### Board
Select this option to create a button grid with a custom number of rows and columns.
#### Column
Enter the number of columns to use on the POS screen.
#### Rows
Enter the number of rows to use on the POS screen.
#### Vertical
Select this option if the POS screen is used in portrait mode instead of landscape.
#### Selection
Select this option if this group is going to be used as a modifier selection screen allowing only a specific number of choices.
#### Choices
Enter the number of choices that will be allowed before the POS returns to the previous screen.
### Options
#### Assign to invoice
...
#### Number of mandatory keys before using any other of this group's keys
...
### Links
#### Corporative communication
...
### Button grid
Click on the Buttons tab. This will display a grid of buttons arranged in the number of columns and rows defined in the Configuration screen. This functions as a preview of what the resulting POS screen will look like.
Related Topics
[Groups and Keys](/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys.md)
[Group Configuration](/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/group-configuration.md)
[Button Configuration](/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/button-configuration.md)
[Button Functions](/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/button-functions.md)
[Button Functions - Detailed List](/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/button-functions-detailed-list.md)
---
# 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://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys/group-configuration.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.