> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/manage-your-workspace/creating-groups.md).
# Creating groups
#### Use groups to organize support teams
You can group agents based on skills and assign groups of agents to your [departments](/manage-your-workspace/creating-a-department.md).
To create a group of agents go to the dashboard sidebar and select **SETTINGS > Teammates & Groups**.
After assigning a name to your group (e.g., Sales, Support, etc.), create the new group by clicking the **Create Group** button.
Once the group is created by clicking the Create Group button, click **Continue** to go to the **Edit Group page**. There, you can add members to the group by clicking the **Add members** button.
Now select the teammates you want to add to the group, then click the **Add button**.
That's all Tiledesk folks.
For any feedback or issue, feel free to pop in on our[ Discord channel](https://discord.gg/nERZEZ7SmG) 📣
For more info on who we are, what we do, or what is our shtick, visit[ Tiledesk.com](https://tiledesk.com/) 👩🚀
---
# 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://guide.tiledesk.com/manage-your-workspace/creating-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.
