Publish and versions

A Journey has a draft and a live version. People see the live one. You work on the draft.

Save and publish

The button at the top right of the editor has two actions.

After you publish, the Journey shows Published.

What happens to a Journey that is in use

Your product, the public link, and the embed all load the live version when the Journey opens. So the next person who opens it sees your change. You do not release a new app.

A person in the middle of a Journey finishes the version they started.

Change a live Journey

Edit and press Save Draft as often as you like. The live version does not change until you press Publish to Live.

To check a draft before it goes live, open Share and scan the code: the phone preview shows your last saved version, published or not.

Version history

Every save is a version. Open the version menu beside the Journey's name.

Pick an older version to open it. It loads as unsaved changes: press Save Draft to keep it.

Name or restore versions opens the full list. There you can name a version, preview it, and Restore it. Restoring makes it your latest draft. It does not publish it.

FounderHQ keeps your newest 30 versions, plus the live one.

Take a Journey offline

There is no unpublish. To close the public link and the embed, open Share and turn off Share publicly. To stop it inside your product, remove it from your app or revoke its key. See API keys.

When someone else saved first

If a teammate saved a newer version while you worked, publishing tells you. Publish again to make your version live, or open theirs from the version menu first.

Duplicate or delete

In Journeys, open a Journey's menu.

• Duplicate makes an unpublished copy.
• Move to brand moves it to another brand.
• Delete removes it for good.

AI agent or LLM? Read this page as markdown