> 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/settings/groups/edit-group.md).

# Edit group

Make changes to an existing group.

Account administrators can edit a group to update its general information, manage its members, and adjust buyer settings. 

* Buyer access can be configured as either full or restricted, depending on the group’s needs.
* For a default group, you can update the group’s general information and manage its members. The modules enabled for a default group cannot be changed. 
* You can update buyer visibility only if the Marketplace module is enabled for the group. If the module was not enabled during group creation, you can enable it while editing the group, if the group is not a default one.
* Buyer access restrictions apply only to the **Marketplace** module.

### Edit a group

To edit a group:

1. Go to **Settings** > **Groups**.
2. Select the actions icon (**•••**) for the group, then select **Edit**.
3. In the **Edit group** flow, do the following as needed: 
   * **General** – Update the group's name and description.
   * **Modules** – Update the modules that the group can access. Note that access can't be updated for a default group.
   * **Extensions** – Choose whether group members should have visibility limited to a selected extension or full visibility across all extensions.
   * **Buyers** – Update buyer settings for the group. This section appears only if the **Marketplace** module is enabled for the group.
   * **Users** – Add or remove group members. 
4. Select **Save**. A confirmation message is displayed stating that the group has been updated.


---

# 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/settings/groups/edit-group.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.