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

# Publish and execution scope

> Choose who can use an automation and which team runs it.

Publishing makes one saved revision available to an audience. Draft changes do not affect the
published automation.

| Audience | Who can use it |
| - | - |
| **Service desk agents in selected teams, from Web** | Service desk agents in the teams you choose, not all team members |
| **Everyone in the organization, from any activated Slack, Teams, Email, Web** | Any employee in the organization, subject to channel and availability rules |

Every production run still needs an execution team for authorization, connections, and limits.

## Requests from Slack, Teams, and email

Flow does not show team-scoped automations to requesters in Slack, Teams, or email channels.
Belonging to a selected team does not change this restriction or grant service desk agent access.

Choose the organization audience for requester-channel discovery. This choice does not make
the automation available in every channel: the channel must route requests to the automation's
owning team. The current published version must also support the channel and meet the existing
authorization, audience, readiness, configuration, and availability requirements.

## Publish an automation

<Steps>
  <Step title="Open the automation and save your changes." />

  <Step title="Select Publish." />

  <Step title="Choose an audience and review its channel limits." />

  <Step title="Select a ready connection for each required integration and team." />

  <Step title="For schedule or event triggers, choose the service account under Automated execution → Run as." />

  <Step title="Review the selected version, diagnostics, Validation scenario readiness, triggers, and audience." />

  <Step title="Select Publish automation." />
</Steps>

Flow blocks publication when a required connection, service account, approval procedure,
Validation scenario review, or automation diagnostic is not ready.

Changing the audience or execution setup requires publishing again. Active runs keep the version,
team, connections, and identity they started with.

## Stop new runs

Open the automation's row actions, select **Unpublish**, and confirm. Saved revisions and run history
remain available to authorized operators.

## Related topics

* [Inputs and approvals](/automations/build/inputs-and-approvals)
* [Versioning and organization](/automations/manage/versioning-and-organization)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.