> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/task-sequences/adding-and-removing-groups.md).
# Adding and removing groups
## Adding a group
As with steps, to add a group, open the task sequence and click the blue **Edit mode** button in the upper-left corner. Once in edit mode, the button will be replaced with a "Save all changes" button and a "Cancel" button.
There are several ways to add groups. The **Add group** button in the **Task sequence version editor** frame adds a group to the task sequence. By default, it is added at the end, but you can move it to the desired location.
Another way to add a group is to go to the group where you want the new group and click the black-and-white folder icon to the right of the blue folder icon and group title.
## Removing a group
{% hint style="info" %}
Removing a group will also remove all of the groups and steps inside of the group, potentially removing important processes from the task sequence.
{% endhint %}
To remove a group, enter **Edit mode**, hover over the group, and click the trash bin icon. The trash bin icon turns red when you hover over it. Click the icon to remove the group from the task sequence.
---
# 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://documentation.2pintsoftware.com/deployr/task-sequences/adding-and-removing-groups.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.
