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

# Flows overview

> Learn what flows are for, how they work, and how to manage them in Flowboard Studio.

A flow is the onboarding journey your users see in your app. It can introduce your product, ask questions, highlight features, request permissions, show a paywall, or guide a user to their activation moment.

## What flows are made for

Use a flow when you want to:

* Welcome new users
* Personalize the first-run experience
* Explain product value before a paywall or signup step
* Collect answers that shape the user journey
* Encourage a key action such as enabling notifications or completing setup

/

## How a flow works

In Flowboard, a flow is made of screens shown in sequence. Each screen contains content blocks such as text, images, buttons, inputs, and progress indicators. Users move through the flow based on the actions connected to those blocks.

Most teams work with flows in this order:

<Steps>
  <Step title="Create the flow">
    Start from AI, a template, or a blank canvas.
  </Step>

  <Step title="Build the screens">
    Add and arrange screens in the left sidebar, then edit the selected screen in the canvas and properties panel.
  </Step>

  <Step title="Preview the journey">
    Review both the screen design and the path from one screen to another before you publish.
  </Step>

  <Step title="Publish the live version">
    Publish when the draft is ready. Your live app continues using the published version until you publish again.
  </Step>
</Steps>

## Draft version vs live version

Flowboard separates the version you are editing from the version your users can see.

<CardGroup cols={2}>
  <Card icon="pen" title="Draft version">
    Use draft mode for editing, reviewing, and preparing changes. Draft updates do not affect your live users.
  </Card>

  <Card icon="rocket-launch" title="Live version">
    The live version is the published flow currently available in production.
  </Card>
</CardGroup>

This separation is important because it lets you keep improving a flow without interrupting the experience that is already running in your app.

## What you can manage inside a flow

<AccordionGroup>
  <Accordion title="Screens">
    Screens are the pages of the journey. You can add, duplicate, reorder, or remove them to shape the sequence.
  </Accordion>

  <Accordion title="Content and layout">
    Each screen can include text, buttons, media, inputs, and layout blocks. Use the visual editor to control hierarchy, spacing, and emphasis.
  </Accordion>

  <Accordion title="Flow name and organization">
    Give each flow a clear business name so your team can identify it quickly in audiences, Labs, and analytics.
  </Accordion>

  <Accordion title="Preview">
    Use preview tools to inspect both the design of an individual screen and the full route map of the flow.
  </Accordion>

  <Accordion title="Publish">
    Publishing turns the current draft into the live version that audiences and experiments can serve.
  </Accordion>
</AccordionGroup>

## Best practices for end-user onboarding flows

* Keep each screen focused on one decision or message.
* Put the most important action on the screen once, with a clear label.
* Use short titles and supportive body copy.
* Remove steps that do not clearly help activation or conversion.
* Publish small improvements often instead of waiting for a full redesign.

## Related guides

* [Manage translations](/features/flows-translations)
* [Set up actions and transitions](/features/flows-actions-transitions)
* [Target flows with audiences](/features/audiences)