> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/creating-flows/building-a-new-flow/organizing-using-groups.md). # Groups Groups are helpful organizers for steps. **Groups** help structure your flow by organizing steps into logical sections. They support conditional logic, custom styling, and dynamic ordering, making it easier to manage and present complex forms. Groups themselves are not content, but help keep your flow and studio organized by acting as containers for **steps**. They can: * be [conditionally enabled](/conditions-and-logic.md), which will either hide or render the steps inside. * use their own styling that overrides the flow theme. * be dynamically re-ordered using the [Group Ranking API](/form-behavior-settings/variant-settings/group-ranking-api.md). The user moves through the flow starting from the group at the top, down to the last group. This is the default behavior for Formsort. {% hint style="info" %} If you'd like to allow your user to jump around the flow, see our [Navigation Sidebar](/styling/customizing-appearance/content-area-and-form-layout.md#navigation-sidebar). {% endhint %} ## Adding steps to a group

Click "Edit groups" to open the Group menu

To add a group, click **Edit groups** when hovering the left-side groups editor, or click the arrow at the top right. In the expanded group editor, you can add groups and then create steps within them. If you want to move existing steps into a group, you can drag the step into the groups while the group editor is expanded. Alternatively, you can use [cut and paste](/creating-flows/building-a-new-flow/copy-paste-of-form-content.md) steps to re-organize content between groups. If you do not create groups, all steps appear within a *default* group. *** ## Group settings #### Group Label You can add a label to easier identify the function of a Group, e.g. naming a Group "Introduction" if it houses the content/questions related to introducing a user to the form. Group labels are not shown to users, unless you choose to show them within the [progress bar](/styling/customizing-appearance/progress-bars.md#counting-groups-or-steps). #### Group ID Used to create a stable definition/ID of the group when using the [Group Ranking API](/form-behavior-settings/variant-settings/group-ranking-api.md). See the linked documentation for more information. *** ## Group logic Groups can be made [conditional](/conditions-and-logic.md), which will show or hide all the steps within a group all at once.

Rendering a group based on a external variable being passed in at flow load.

## Style ### Styling groups [Group style overrides](/css-and-advanced-styling.md#group-style-overrides) can be used to alter any part of the general Theme set within a group.

These are particularly handy if you have distinct sections of a flow which might want to adopt a slightly different look and feel. For example, you might have an *Introduction* group that contains some lightweight questions and content perhaps a more colorful and spacious design. You can follow that with a *Data collection* group that has a denser layout to facilitate answering many questions all 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.formsort.com/creating-flows/building-a-new-flow/organizing-using-groups.md?ask=&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.