Channels & rollout
Choose what a channel serves in test or production, without shipping a new app build.
What channels do
A channel is the address your app resolves. Your app points the Rheo SDK at one channel id. Rheo serves the assignment on that channel.
Channels exist separately in test and live environments. Use test channels for QA and staging. Use live channels for real users.
Publishing a flow does not put it in front of anyone. You publish a version in the builder, then pin that version on a channel when you are ready. Users pick up the change on their next session.

How your app connects
Your developers configure two things in the SDK:
- Publishable key: identifies your app and whether traffic is test or live
- Channel id: picks which channel within that environment
Rheo looks up the channel and returns a content kind. A flow pin returns a published flow. A banner pin returns a published banner. A code pin returns a variant key and parameters. An experiment returns one variant of that experiment. When you change the assignment, Rheo bumps an internal version counter so clients know to refresh.
See Channel (concept) for a short mental model.
What a channel can serve
Open Convert → Channels, select a channel, and choose Change.
| Choice | What users get |
|---|---|
| Pin a flow version | One published flow version. Drafts cannot be pinned. Publish first. |
| Pin a banner version | One published banner version. Drafts cannot be pinned. Publish first. |
| Pin code parameters | One variant key and a flat parameter object. The host reads values with get. |
| Run an experiment | A running experiment (flow, banner, or code content kind) that belongs to this channel. Starting an experiment does not attach it. Attach it here when it should serve. |
Clear removes the assignment. The next resolve is unassigned.
While the channel is serving an experiment, another pin or a different experiment is rejected. Stop that experiment first. A pin or an empty channel can be replaced.

Rollout approvals (Scale plan and above)
On Scale and Enterprise plans, workspace owners can require a second pair of eyes before a channel assignment goes live.
Configure the policy at Account → Approvals:
| Setting | What it does |
|---|---|
| Require approval for channel rollouts | Master on/off switch |
| Testing channels | Changes in the test environment need approval when enabled |
| Production channels | Changes in the live environment need approval when enabled |
| Approvers | Selected editor teammates who can approve or reject |
Indie and Grow workspaces see an upgrade prompt instead. Non-owners can view the policy but cannot change it.
Approvals apply to what the channel serves. Editors can still publish new flow or banner versions immediately. Pointing a channel at a flow or banner version, editing a code pin, attaching an experiment, pinning a winner, or clearing the channel may need sign-off.
A request stores one snapshot: a flow version, a banner version, a code key and parameters, an experiment, or a clear. A channel has one open request. That request blocks every other write to the assignment, including people who could otherwise change it directly.
When approvals are on
- An editor proposes the next assignment and adds a short description.
- Approvers get a notification and review the snapshot.
- On approve, the channel updates. Approving a winner pin or a clear for the experiment the channel is serving also marks that experiment stopped.
- On reject, the previous assignment stays in place.
Track open requests from the notification bell or the channel's rollout queue.
Archive old channels
When a launch is done, archive channels you no longer need. Archived channels are hidden from normal lists. If an old app build still points at an archived channel, those users will not receive an assignment.
Plan limits and permissions
- Editors can change channel assignments. Viewers can see them but not change them.
- Channel counts are capped per environment by plan (for example, Indie allows one test and one live channel).
- Rollout approvals require Scale or above. See Plans & entitlements.
Troubleshooting
| Symptom | What to check |
|---|---|
| No versions in the flow or banner picker | Publish the flow or banner, or fix validation errors in the builder |
| Change is rejected while an experiment is serving | Stop that experiment, or pin its winner, before assigning something else |
| Approval request stuck | Confirm approvers are still editors and the policy covers the right environment |
| Users still see old content | Confirm the channel assignment and that the app resolved again after the version counter changed |