> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/teams-users-and-custom-fields/generating-reports.md).

# Generating reports

Generate detailed reports by filtering team data based on various criteria, and export it as an Excel file for easy analysis and tracking.

### Running Team Reports

The reporting tools in Eventflow allow you to gain deeper insight into your teams by applying filters and exporting data. This is useful for monitoring engagement, understanding team structures, and managing onboarding progress.

#### Step-by-Step: How to Run a Report

1. Navigate to the Manage Teams section in the admin dashboard.
2. At the top of the page, you’ll find filtering options to help refine your report:

   - Team Type: View only teams belonging to a selected type. - Not Logged In: Identify teams whose members have not yet logged into the platform. - Stand Share: Filter based on whether teams are sharing stand space (if applicable).
3. Once you’ve selected your desired filters, click the Generate Report button located on the right-hand side of the page.
4. An Excel (.xlsx) file will be downloaded containing all filtered team data, including any custom fields you’ve configured.

This export provides a full overview of team information, making it easy to track participation, follow up with inactive users, and tailor communications accordingly.


---

# 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.eventflowapp.com/eventflow-cms/teams-users-and-custom-fields/generating-reports.md?ask=<question>&goal=<user_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.