> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/chat/manage-group-chats.md).

# Manage group chats

Add participants, edit the chat name, or leave a group chat.

### Add a member to an existing chat

If you are in a chat conversation, you can quickly add someone from your account to the chat. New users added to the chat can view all previous messages from the beginning of the chat.

To invite participants to a chat:

1. On the **Chats** page, open the desired chat conversation.
2. Select the actions icon (**•••**), then choose **Add participant**.
3. In **Add participant**, select the user you want to invite. You can select multiple users. When done, select **Add**. 

### Edit the chat name or logo

To edit the chat name or logo:

1. On the **Chats** page, open the desired chat conversation.
2. Select the actions icon (**•••**), then choose **Edit**.
3. In **Edit group chat**, edit the chat group name and upload a new image as necessary.
4. Select **Save**.

### Leave a group chat

To leave a group chat:

1. On the **Chats** page, open the desired chat conversation.
2. Select the actions icon (**•••**), then choose **Leave**.
3. In the **Leave chat** confirmation, select **Leave** to confirm.


---

# 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.platform.softwareone.com/modules-and-features/chat/manage-group-chats.md?ask=<question>&goal=<user_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.