> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/lgd-features/chat/group-chats-vp.md).
# Group chats (VP)
A chat is accessible in the lobby and every session. Use the chat to chat with other users. In the company booths, you can also find a chat.
{% hint style="info" %}
**Note:** For program items, you can choose whether you want to have the chat function enabled or disabled. For more information about programme settings, please visit [this article](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/application-1/programmes).
{% endhint %}
{% hint style="info" %}
**Note:** Clear the entire chat by typing /clean or clicking the red icon in the top left corner of a message to delete a selected chat message.
{% endhint %}
It is also possible for attendees to create private group chats between themselves. By clicking on the chat -> create new chat button, you can select which attendees to create a chat with. This can also be used for organisers to create a group chat with other hosts, speakers and moderators. This chat can then be used for quick communication during the event.
---
# 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://knowledge-base.letsgetdigital.com/lgd-features/chat/group-chats-vp.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.