> For the complete documentation index, see [llms.txt](https://docs.flytbase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flytbase.com/in-flight-modules/annotations/organizing-and-customizing-annotations-groups.md).

# Organizing and Customizing Annotations: Groups

## Groups & Sub-Groups

Annotations can now be structured using Groups and Sub-Groups, allowing teams to categorize annotation data by region, mission phase, or type of activity.

* **Group:** Creates a top-level group.
* **Sub-group:** Creates a sub-group under the group that is currently selected.

### To create a group or sub-group:

* Click **Add** in the Annotations panel

<figure><img src="/files/dRiiTOIhb6iOIqF49Q47" alt=""><figcaption><p>Option of Adding a new group of annotations on the FlytBase dashboard</p></figcaption></figure>

* Select **Group** or **Sub-Group**

<figure><img src="/files/eXFz4kgN3NECu8HKkXw2" alt=""><figcaption><p>Select Group or Sub-Group as per your requirement</p></figcaption></figure>

* Enter a name and start organizing your annotations accordingly.

### To create a sub-group under a specific group:

* In the Annotations panel, click on the group under which you want to create a sub-group
* Then, click the ![](/files/Hmjh1iQZ8lI85bpS4mCi) icon beside it to automatically add a sub-group within that group

<figure><img src="/files/7mnMXqX8Yyn4ceeRnhsp" alt=""><figcaption><p>New Sub-group added</p></figcaption></figure>

You can rename, delete, or hide groups and sub-groups as needed. Hiding a group hides all annotations under it on the map, making it easier to declutter the interface during active missions.

You can choose to hide individual annotations manually, or quickly hide all annotations at once by toggling visibility on the entire group.

Toggling a group's visibility will show or hide all the annotations under it on the map.

<figure><img src="/files/oAk6kiQzoF1Uhig926Da" alt=""><figcaption><p><em>Five annotations displayed on the map under a single group</em></p></figcaption></figure>

Click on the <img src="/files/ULt5WrGVWVuKC8Rn6p3X" alt="" data-size="line">symbol in front of the group to hide all annotations under that group.

<figure><img src="/files/cDDHLZVP3TsQhw0z3vjT" alt=""><figcaption><p><em>Hiding the group removes all five annotations from the map view</em></p></figcaption></figure>

You can use sub-groups to break down complex areas, like different floors of a building or sections of a large inspection zone.&#x20;

### Multi-select and bulk actions

You can act on several items at once.

* Use the checkbox on a group or annotation row to add it to the selection.
* Hold **Ctrl** (Windows/Linux) or **Cmd** (macOS) while clicking a row to add or remove it from the selection.
* Use the top checkbox to clear the selection.

<figure><img src="/files/dYf9RCXumUcEXc7katcY" alt="" width="140"><figcaption></figcaption></figure>

When you have one or more items selected, a **Bulk actions** button appears at the top of the list with these options:


---

# 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.flytbase.com/in-flight-modules/annotations/organizing-and-customizing-annotations-groups.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.
