Skip to content

Sharing a flow and its results (read-only)

Send a client a clean page showing the work and the outputs — no account needed, no editing, no keys, cost hidden by default, revocable in one click.

In this article (6)

The alternative to zipping up thirty images and writing an email about which is which. A share is a clean, public page showing the flow and — if you include it — a run's results, with every item's inputs visible so the client can see what produced what.

Creating one

Press Share on a workflow card, or in the Builder top bar. One dialog, two ways:

  • Anyone with the link — create it and send it. No sign-in needed to view.
  • By email — add a person's email. You get a link to send them, and if they have a FlowArray account the flow also appears under Shared with me on their Workflows page.

Options worth setting deliberately:

  • Include the latest run's results — off means they see the flow only.
  • Expire in 7 or 30 days — or never.
  • Show run cost to viewersoff by default. Turn it on for internal review; leave it off for a client share. Your cost is not their business.

What a viewer gets

  • The flow, the outputs, and each item's Inputs (the reference images and field values behind that result).
  • Text rendered properly, images full size.
  • Big runs stay usable: images load as you scroll, and results show the first 48 with a Show more.

What a viewer can never get

  • No editing and no running. Nothing on that page can spend your money.
  • No API keys, no pool names, no credentials. They are stripped server-side, not merely hidden.
  • No other flow, run or output in your workspace — a share is scoped to exactly what you shared.
  • No cost, unless you switched it on.

Revoking

Revoke in the same dialog kills the link immediately, including any image the page was serving. If you are unsure who has a link, revoke it and create a new one.

Sharing with a colleague instead

Someone who should build or run does not need a share — invite them as a member, or as a viewer if they should only look. A share is for people outside the workspace.

Want feedback, not just visibility?

Turn the share into a review surface: see the approval portal, where reviewers can approve or request changes per item and leave comments.