> 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/devices/fleet-overview/choose-your-fleet.md).

# Choose Your Fleet

Choose the fleet where you will view data and deploy software updates.

The Fleet is the highest organizational level in a JFrog Connect account, and each fleet is an entirely separate environment that enables you to differentiate between users and devices that belong to a different product or use case. Therefore, each fleet has its own devices, settings, and properties.

The main pages in Connect (Overview, Devices, and Deployments) and all the remote tools act and display data within a single fleet.

The first time you log in, Connect will display data from the default fleet. Once you add more fleets, Connect will show data from the last fleet you displayed before logging out. The Fleet dropdown box appears in the top menu of Connect.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/FLkNzInK966UaKdINuuu/choose-your-fleet-nui-01.png" alt="" width="563"><figcaption></figcaption></figure></div>

## Prerequisite

* Two or more fleets defined in Connect

## Choose Fleet

To choose a fleet to work in, do the following:

* In the Fleet dropdown box, click the fleet you want to use.

## What's New?

Learn how to [create a new fleet](/features-new-ui/account-management/organize-your-fleet/create-project.md).


---

# 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/devices/fleet-overview/choose-your-fleet.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.