# Flows

"Flows" gives you the ability to access all flows created in your Appmixer instance – flows used by you or your team as well as those used by your end-users.

!["Flows" overview](/files/-MhiO1Mg7jPzyy95cmHE)

As you can see in the overview above, you can see a few flow attributes:

* Flow name
* Stage (stopped or running)
* User (user who created the flow identified by email)
* Created (time at which the flow was created)
* Modified (last time at which the flow was modified)
* \# of Components (number of components used in the flow)
* Thumbnail (downloadable picture of the flow setup)
* Flow description (flow description written in JSON including the flow ID)

{% hint style="info" %}
The "Flows" tab can be used by your support for troubleshooting purposes as it offers a complete and in-depth look at all flows created by your end-users.
{% endhint %}

Notice that if you click through the flow name, a modal pops up showing you the Messages count and Messages size.

![Messages count and size](/files/-Mhm7mCBqvazQA8tnpBM)

Furthermore, you can filter all flows either by flow name or stage (stopped or running) to narrow down your search results.

As already mentioned, "Flows" tab can be very helpful for your support team while troubleshooting errors in your end-users flows. The reason being is that the "Flow description" on the very right side offers an in-depth view of the flow setup (in a JSON format).

![Flow description](/files/-Mhm90tYWrMlnTMkGwNa)

Now that you know a little bit about how Appmixer Backoffice works, [let's have a look at ways to manage users in your Appmixer instance](/kb/backoffice-features/users.md).


---

# 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.appmixer.com/kb/backoffice-features/flows.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.