> For the complete documentation index, see [llms.txt](https://docs.verge.aero/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.aero/drone-show-software/verge-web-portal/fleets/fleet-management.md).

# Fleet Management

The Fleet Management page lets you create new fleets, delete empty ones, move devices between fleets, and rename fleet regions. Navigate to [**Fleet > My Fleets**](https://github.com/Verge-Aero/VergeDocs/blob/main/fleet/fleets/README.md) in the Verge Aero Portal to access these tools.

<figure><img src="/files/MdKnRUensAr9LMqXIbp4" alt="My Fleets page showing three fleets — New York X1s, Los Angeles X1s, and North America X7s — with Create Fleet, Transfer Devices, and Upload FAA Data buttons at the top"><figcaption><p>The My Fleets page with fleet management controls. Each fleet row includes a <strong>view</strong> button, a transfer icon, and a delete icon.</p></figcaption></figure>

***

## Creating a Fleet

Select **Create Fleet** from the My Fleets toolbar to open the fleet creation dialog.

<figure><img src="/files/8rnXdWKwhrtbYfi6zeuH" alt="Create Fleet modal with X1/X7 selector, Region text field, and optional Devices CSV upload"><figcaption><p>The Create Fleet modal. Device type, region, and an optional initial device CSV can all be provided at creation time.</p></figcaption></figure>

Fill in the following fields:

| Field           | Required | Description                                                                                                                 |
| --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Device Type** | Yes      | Select **X1** or **X7**. This determines which drones can be assigned to the fleet and cannot be changed after creation.    |
| **Region**      | Yes      | A label that identifies where or how the fleet is used — for example, `North America`, `Los Angeles X1s`, or `EU Tour`.     |
| **Devices CSV** | No       | A plain-text or `.csv` file containing a flat list of device identifiers to add to the new fleet at creation, one per line. |

Select **Create Fleet** to confirm. The new fleet will appear immediately in the fleet list.

### Adding Devices at Creation Time

If you supply a Devices CSV, each identifier in the file is looked up and validated before being moved into the new fleet. The Portal accepts two identifier formats:

* **X1 serial numbers** — used for X1 drones (e.g. `6340`)
* **Full UIDs** — used for X7 drones (e.g. `P8DR4T3U96`)

A device is only moved if all of the following are true:

1. The identifier matches an existing device in the system.
2. The device currently belongs to a fleet that your organization owns.
3. The device type matches the fleet type — X1 serials can only go into X1 fleets, and X7 UIDs can only go into X7 fleets.

After the fleet is created, a success notification confirms how many devices were added. If any identifiers in your file did not meet the criteria above, a warning notification lists them so you can investigate.

{% hint style="info" %}
You can always add devices to an existing fleet later using the **Transfer Devices** flow described below.
{% endhint %}

***

## Transferring Devices Between Fleets

Devices can be moved between fleets at any time using the **Transfer Devices** action. This is useful when reorganizing a fleet, splitting a large fleet into regional groups, or consolidating devices before a show.

There are two ways to open the Transfer Devices dialog:

* **From the fleet list** — select the **Transfer Devices** button in the toolbar (no source fleet pre-selected), or click the **↔** icon on a specific fleet row to pre-fill the source context.
* **From inside a fleet** — select the **Transfer Devices** button in the fleet detail header to transfer devices out of the currently viewed fleet.

In the dialog, select a **target fleet** from the dropdown and upload a **Devices CSV** (same format as above). The same validation rules apply — only devices your organization owns and of the matching drone type will be transferred. Any identifiers that do not qualify are listed in a warning notification after submission.

{% hint style="info" %}
The target fleet dropdown is automatically filtered to show only fleets of the same type as the source fleet (X1 or X7) when a source fleet is pre-selected.
{% endhint %}

***

## Renaming a Fleet Region

The **Region** field is the primary label for a fleet. To rename it:

* **From the fleet list** — click the **pencil icon** (✏) next to the region name in the table row.
* **From inside a fleet** — click the **pencil icon** in the fleet detail header, next to the fleet stats bar.

<figure><img src="/files/ibIK15zmgMFKcp9RtCnD" alt="Fleet detail view for New York X1s showing the Return to Fleets button, Transfer Devices button, pencil rename icon, download icon, and drone count stats"><figcaption><p>The fleet detail header. The pencil icon opens the Rename Region dialog; the transfer icon opens the Transfer Devices dialog scoped to this fleet.</p></figcaption></figure>

A small dialog will appear with the current region name pre-filled. Edit the name and select **Save**. The change takes effect immediately across the Portal.

***

## Deleting a Fleet

A fleet can only be deleted when it contains **zero devices**. On the fleet list, the **trash icon** for a non-empty fleet is disabled — hovering over it shows the tooltip *"Fleet must be empty to delete."*

Once a fleet is empty, the trash icon becomes active. Clicking it opens a confirmation dialog that asks you to confirm before proceeding. Deletion is permanent and cannot be undone.

{% hint style="warning" %}
To delete a fleet that still contains devices, first transfer all of its devices to another fleet using the Transfer Devices flow described above.
{% endhint %}