> 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.md).

# Fleets

The **Fleets** workspace is where your organization's hardware lives. Every drone, battery, charger, gateway, base station, and pyro board your team operates is represented by a **device** in the Portal. Devices are organized into **fleets** — region- and type-scoped groups (X1 or X7) that map to how your operation is actually run — and then surfaced through a handful of tools that take you from day-to-day fleet management through repair tracking and physical shipment.

This section is organized around four features, each of which has its own page:

1. [**Fleet Management**](/drone-show-software/verge-web-portal/fleets/fleet-management.md) — create new fleets, move devices between them, rename regions, and remove fleets that are no longer in use. The foundation everything else builds on.
2. [**Device Groups**](/drone-show-software/verge-web-portal/fleets/device-groups.md) — assemble reusable, ad-hoc groups of devices that cut across fleets. Useful when you need to act on the same set of drones repeatedly — to spin up a new regional fleet, file an RMA, send a CSV to support, or export an inventory report.
3. [**RMA Requests**](/drone-show-software/verge-web-portal/fleets/rma-requests.md) — open, track, and close Return Merchandise Authorizations for devices that need repair. The RMA flow scans the affected devices, captures per-device notes, and routes the request to Verge's support team.
4. [**Inventory Tracking**](/drone-show-software/verge-web-portal/fleets/inventory-tracking.md) — pack drones into physical cases and pallets, mark shipments as sent / received / completed, and label everything with scannable QR codes for end-to-end tracking before and after a show.

> **Tip:** Devices appear in only one fleet at a time, but they can belong to any number of Device Groups simultaneously. Reach for fleets when you're modelling **where the hardware lives**, and for groups when you're modelling **a set of devices you'd like to act on together**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verge.aero/drone-show-software/verge-web-portal/fleets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.