User Guide
Flows
Create, version, publish, and retire onboarding flows from the Rheo dashboard.
What is a flow?
A flow is the versioned onboarding experience you design in Rheo: screens, branches, paywalls, and motion. Flows do not go live on their own. A channel pins a published flow version, or a flow experiment variant serves one, before end users see it. A channel can also pin code parameters instead of a flow.

Lifecycle
- Create — From Convert → Flows, create a blank flow, start from a template, import a bundle, or paste a manifest. Open Edit to enter the flow editor. Use Rheo Agent on Grow+ after the flow exists — create does not generate with AI.
- Draft — The editor autosaves as you work. Rheo checks your flow for common issues (missing connections, disabled integrations, and similar) before you can publish.
- Publish — Publishing creates an immutable version that channels and experiments can pin. Unpublished drafts never affect live users.
- Duplicate — Copy a flow when you want to try large structural changes without changing the original.
- Retire — Archive or stop assigning flows when a campaign ends. Keep each channel pointed at an active published version.
Versioning
Each publish creates a new version you can label and browse from the flow editor. Analytics and experiments can filter to a specific version so you do not mix audiences from before and after a change.
Channels and experiments
- A flow pin on a channel serves one published flow version.
- A flow experiment serves one published version per variant. The channel serves that experiment only after you attach it. See Experiments.
Limits and permissions
- Publishing may require a specific workspace role, or approval on sensitive channels (Scale plan).
- Flows that use partner integrations (for example RevenueCat or Superwall paywalls) require those integrations to be enabled for the app — otherwise publish is blocked with a clear message. Headless surfaces do not need an App settings toggle.