# Groups & Reports

Loadmill provides functionality for creating logical groups. Groups serve as a mechanism for teams to take ownership of test suites and flows. They allow for the segmentation of reports based on performance and facilitate understanding of ownership within different groups. Being part of a group makes it easier to avoid confusion about test responsibilities and enables better focus on owned areas.

Here is a group creation example:

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LHDbUNdi3wPd9vSolzU%2Fuploads%2Ft1rdtePUpG7EfhFbF6lm%2FGroupCreation.mp4?alt=media&token=e6263908-2064-4a70-994b-817062de375c>" fullWidth="false" %}

### Assigning Tests to Groups

You can assign your Flows/Suites to groups. To do so, navigate to the desired flow/suite, and click on the 'Assign group' button located at the top (![](/files/3OqAWAOsFr4Jbm4Ts2Io)), then choose the group you want to assign the test to.

> Assigning a suite to a group takes precedence over assigning a group to a flow. For example, if group X is assigned to a suite, and group Y to a flow inside the suite, the test will be counted as belonging to group X.

### Reports Dashboards

Viewing group-filtered reports is convenient. Simply navigate to Reports -

<figure><img src="/files/0RX5Wxzrbx1sP9Dos5kA" alt=""><figcaption></figcaption></figure>

Where you can filter the displayed statistics for a specific group within the available options.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LHDbUNdi3wPd9vSolzU%2Fuploads%2FzRvJp9OiZS2HRguqIyf6%2FDashboards.mp4?alt=media&token=77ad0012-fdb1-417b-9019-b409b7c121fe>" %}


---

# Agent Instructions: 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:

```
GET https://docs.loadmill.com/collaboration/groups-and-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.