> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/account-management/organize-your-fleet/create-groups.md).
# Create Groups
Groups can help you segment your fleet into manageable subsets of devices. This page describes how to create a group in JFrog Connect.
[Groups](/features-new-ui/account-management/organize-your-fleet.md#groups) are an essential tool for dividing up your fleet of devices into manageable subsets. It is worth taking some time to think about how you want to organize your groups so that you can manage your devices efficiently.
Your default fleet that is created when your JFrog Connect account is created contains two default groups, Test and Production. You can change the names of these, create additional groups, and create sub-groups within groups.
Within a fleet in Connect, you can have two levels of groups, for example, a top-level of groups and one level of sub-groups under each group at the top level.
## Create a Group
You can create a group if you have the permission: Manage groups.
To create a group, do the following:
1. Go to the **Fleet Tab** in the Fleet Settings page, and go to the **Group Configuration**.
2. Enter a name for the group.
3. Choose the position of the group in your fleet hierarchy. For example, choose **Main Hierarchy** if you want the new group to be at the top level. If you choose a different item in the dropdown list, the new group will be a subgroup, i.e., a group at the level under that item.
4. Click **Create Group**.
## What’s Next?
Learn how to [add a device](/features-new-ui/account-management/organize-your-fleet/create-groups/add-device-to-group.md) to a group.
---
# 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.connect.jfrog.io/features-new-ui/account-management/organize-your-fleet/create-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.
