Appearance
Publish & share
Every page you build in the designer has two lives: the working draft you keep editing, and the published snapshot the public sees. This page explains the publish gate, the public URL, per-page visibility, and the two buttons that do the work.
Draft vs. published
While you are building, your saves land in the project's working copy. That is what you preview inside the editor. The public page, though, is served from a separate published snapshot — a frozen copy taken the moment you press Publish.
This split is deliberate. It means you can keep editing, saving, and rearranging a page without any of those changes leaking out to visitors mid-edit. Nothing is live until you say so.
Under the hood, publishing copies the file's working data into a published slot on the project and stamps a publishedAt timestamp. The public page always prefers that snapshot. The one exception: a form that has never been published falls back to its working copy, so a brand-new page is viewable straight away — but as soon as you publish it once, the snapshot takes over and future edits require a fresh publish to go live.
IMPORTANT
After a page has been published once, saving in the editor no longer updates the public page. Press Publish again to push your latest changes live.
The public URL
Published pages live at a predictable, shareable address:
https://your-flowrunner-host/p/<projectId>/<fileId>The /p/ route is a server-rendered page that re-reads from the database on every request, so a fresh publish is reflected immediately — there is no stale cache to wait out. Only files of type form (the designer's page files) can be published or served here.
TIP
Want a cleaner address than /p/<projectId>/<fileId>? Attach a custom domain to the project.
Per-page visibility
Each page carries a visibility setting in its page settings:
| Visibility | Who can view |
|---|---|
| Public (default) | Anyone with the link. |
| Private | Only signed-in members of the project's workspace. |
A private page checks the visitor's session and workspace membership. If they are not a signed-in member with at least viewer access, the page returns a standard "not found" — it does not reveal that the page exists. Use private visibility for internal pages, staging content, or anything you are not ready to expose publicly.
The Publish and Share buttons
Both actions live in the designer's top bar:
- Publish takes the snapshot described above. On success you get a confirmation that the public page now serves this version.
- Share copies the page's public URL to your clipboard so you can paste it anywhere. If your browser blocks clipboard access, it shows the URL in a prompt so you can copy it manually.
INFO
📸 Screenshot — the designer top bar showing the Publish, Share, and Export buttons
Publishing requires editor access to the project. Viewers can open and share public pages but cannot publish changes.