> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fapost.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Flow groups

> Organising flows once there are more than a few.

A group is a folder for flows. Each shows its **name** and how many **flows** it
holds, with **Edit** and **Delete**.

Groups are organisational only. Putting a flow in a group does not change when it
runs, what it can do, or who can reach it — it changes where you find it.

## When they start paying off

With three flows the list is the organisation. With thirty it is not, and the
question becomes what to group by.

Grouping by **purpose** — onboarding, support, sales — matches how people look
for a flow: they know what they want to change before they know what it is
called.

Grouping by **status** — live, draft, retired — works while a lot is being built
at once, but stops being useful when things settle, because a flow's status is
already visible in its row.

Grouping by **trigger type** rarely helps. That information is on the flow itself.

## Deleting a group

Deleting removes the folder, not the flows. They return to being ungrouped, shown
with a dash in the *Group* column on the [flows list](/using/flows).

## Not the same as contact groups

The console has two screens called *Groups*, in different sections, and they are
unrelated:

|                                                                  |                   |
| ---------------------------------------------------------------- | ----------------- |
| **Flow groups** — under *Flow*                                   | Folders for flows |
| **[Contact groups](/using/contact-groups)** — under *Operations* | Lists of people   |

The sidebar section tells you which one you are on.