---
title: "Using Team Flows"
slug: "using-team-flows"
updated: 2026-09-08T16:51:51Z
published: 2026-09-08T16:51:51Z
canonical: "docs.xtremepush.com/using-team-flows"
---

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

# Using Team Flows

If a teammate has already built a flow you need, such as a standard report or a routine data check, Team Flows lets you run it or copy it instead of needing to build your own from scratch.

## Find a flow before you build one

1. Click **Xpert Flows** in the sidebar to expand it.
2. Click **Team Flows**.

Each flow card shows its name, a description of what it does, how many blocks it has, and who published it, so you can judge whether it fits your need before opening it.

## Run it as it is, or make it yours

| If you want to | Do this |
| --- | --- |
| Check what a flow does before running it | Open it to view its blocks and configuration. You cannot edit a Team Flow directly - this protects the published version from accidental changes. |
| Use it exactly as published | Click **Execute**. It runs with its existing configuration, and you can view the results as with any other flow. |
| Adjust it for your own use, for example a different recipient or query | Click **Duplicate** to create your own editable copy in **My Flows**. |

## Share a flow you have built

Once a flow of yours works reliably, publish it so others do not have to build the same thing:

1. Go to **Xpert Flows > My Flows** and open the flow.
2. Click **Publish**.
3. It now appears in Team Flows for everyone in your organisation.

To take it back, open it from **My Flows** and click **Unpublish**. It is removed from Team Flows but stays in your own My Flows.

## Keep shared flows dependable

- Test a flow thoroughly before you publish it.
- Give it a name that tells teammates what it does without them having to open it.
- Add a description covering what it does, what integrations it needs, and any configuration required.
- Avoid making breaking changes to a flow that others may already depend on.