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

# Build paths for different viewers

> Choose when to use a branch, a flow ending, or a sandbox journey.

Not every viewer needs the same story. You might offer a short overview to a buyer and a more detailed workflow to an evaluator. Start by identifying the decision each viewer can make, the screen each choice should reach, and what happens at the end of each path.

## Let a viewer choose

A branch pop-up can offer buttons that lead to different parts of a guided demo:

1. In the editor, open **Flow** and add or select a pop-up where the choice should appear.
2. In the pop-up's **Behavior** section, choose the **Branch** type. Branch availability depends on your plan.
3. Under **Branch options**, add a button for each choice. Give each one a label that describes the outcome, such as “See the reporting workflow.”
4. Open each button's settings and choose its action and destination. A button can continue, go to a step or chapter, open an external URL, or restart the demo.
5. Preview every choice from the beginning, including how each path ends. Check that the destination makes sense without context from a path the viewer did not take.

Use two clear choices before adding more. A branch should help the viewer decide what to see, not make them learn your internal product structure.

## Connect flows at the end

To decide what happens after a flow's final step, open **Flow** → **When this flow ends**. Where another flow is available, you can select it and a destination step. The final guide can also have its own ending behavior, so check that it uses the flow's ending if that is what you intend.

## Shape a sandbox journey

A sandbox represents connected captured pages. Open **Flow** → **Open journey map** to inspect the pages, starting state, links, guided presenter path, and audience-routing options. Capture or connect the pages needed for the routes you want to support, then test those transitions in preview. See [Build and check a sandbox](https://docs.arcdemo.io/guides/sandbox.md) for the page and link workflow. A sandbox is useful when exploration matters; a short guided path is often easier when there is one outcome to teach.

Before publishing, test each intended starting point, branch, and ending. Check the published version again after changes: a saved draft does not update a shared demo until you [publish](https://docs.arcdemo.io/share/publish.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.