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

> ## Agent Instructions
> Flowy is a node-based AI creative platform: you generate images, video, audio, 3D and vector on an infinite Canvas, refine on the Studio timeline, and export or publish from the same project.
> Prefer the Flowy MCP server (https://mcp.tryflowy.ai/mcp) or the REST API at https://apis.tryflowy.ai/v1 for programmatic work. Install with `flowy mcp install` from the @flowy/cli package.
> Credits are workspace-scoped. Generations reserve credits on start and only deduct on success, so failed runs refund automatically.

# Publishing to Community

> Share a project as a template or a flow as a runnable tool, see what becomes public, and undo either one.

Community holds two different kinds of public work: **templates**, which are published projects people remix, and **flows**, which are published apps people run. Publishing either makes it visible outside your workspace. Here's what that means for each, and how [publishing](/community/publishing) works in full detail.

## Publish a project as a template

Only the project's owner can publish it, and the canvas needs at least two nodes before **Continue** unlocks. From the canvas, open **Share → Publish to Community** and fill in a title, description, category, up to five tags, and a cover image or video.

Publishing copies the canvas (nodes, connections, and settings) along with the media it produced into a public tier, so signed-out visitors can preview it. From there, anyone can remix it into a project of their own; remixing never touches your original.

## Publish a flow as a runnable tool

A flow publishes from **App Builder**, where a **Private/Workspace** visibility choice controls who finds it *listed* in your workspace, and a separate **Submit to Community** toggle is what lists it publicly in [Community → Flows](/community/flows).

<Warning>
  Every published flow gets a public run link the moment it's published, no matter its visibility setting. Private and Workspace only control who finds it *listed*. Anyone holding the link can still open and run it.
</Warning>

## What becomes public

For a template, the title, description, category, tags, cover, and the canvas's structure and media are all visible to anyone who opens it. For a flow, its title, description, cover, and the run interface itself are public at its link. The canvas that built it stays private unless you've separately published that project as a template too.

## Undo it

* **Templates**: reopen **Publish to Community** on the project; it's now labeled **Publish updates**, with an **Unpublish** action alongside it. Unpublishing removes it from Community immediately. Remixes others already made are unaffected, and the project itself stays in your workspace.
* **Flows**: there's no visibility downgrade for a flow once it's public. The only way to fully remove one from Community (and everywhere else) is to delete the flow, which also breaks its public link immediately.

<Tip>
  Found something in Community that shouldn't be there: spam, a copyright issue, anything worth a second look? See [reporting](/community/reporting) to flag it from the template's own page.
</Tip>