> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/community-management/integrations/groups.io.md).
# Groups.Io
Connect Groups.io to sync groups and topics activity.
1. On the **INTEGRATIONS** page, you will see all the connectors. Scroll down and check the **Groups.io** connector.
2. Click **Connect**.
3. In the pop-up window, you must authenticate the groups.io account you want to connect to. This secure login process ensures that users are verified and authorized to access the system.
{% hint style="info" %}
Authenticated user accounts are saved at the sub-project level, so no reauthentication is required for new groups within the same sub-project. This process improves user convenience and reduces errors.
If your password changes or you need to switch to a different groups.io account, use the "Reverify account" feature to update your authentication information.
{% endhint %}
4. Enter the Email ID and the password, and click **Verify Account.**
5. After verification, you can connect to both groups and subgroups under **Connect groups**.
* To connect a group, write down the name of the group.
* To connect a subgroup, write down the group name, followed by +, followed by the subgroup name. E.g. groupName+subGroupName
6. Click **Connect.**
7. Verify if the groups.io integration is successfully completed on the **Integration** page.
Activities Collected:
* Messages/emails
* A member joining and leaving mailing groups
---
# 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.linuxfoundation.org/lfx/community-management/integrations/groups.io.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.
