> For the complete documentation index, see [llms.txt](https://help.diarkis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.diarkis.io/en/diarkis-modules/group.md). # Group Module ## Overview The Group module is suitable for building a communication group that involves multi-directional interaction among a large number of users. It can connect users with different network protocols, and there is no limit to the number of users that can be connected. It is well-suited for sending and receiving real-time messages among a large number of participants. However, since there is no limit on the number of participants, if implemented in a way that a large number of users are sending data frequently, there is a possibility of unintentionally increasing the load on both the server and the clients. Additionally, due to the Group module's nature of facilitating communication among a large number of users via inter-server communication, the round-trip time (RTT) tends to be higher compared to the Room module, which operates within the same server. --- # 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.diarkis.io/en/diarkis-modules/group.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.