Task guide

Save, publish and recover work

Know which copy lives in your browser and which copy was published.

Before you start

Prerequisites: A local diagram. An active signed-in account is needed for publishing.
Permissions and plan: Free personal publishing; organization publishing requires its permissions.

Steps

Export a portable file before making a risky change.
Local edits are saved to this browser. Reopen the editor in the same browser to resume the draft.
Sign in and choose Publish to create or update the owned server copy. Wait for the success message.
Open My diagrams and reopen the published diagram to check the server copy.
If a local draft is missing, import your exported backup as a new unpublished copy.

Runnable example

Flowboard Markdown

Copy this model into Import in the editor. Export current work first. The two stable identifiers, api and db, connect the services to the flow.

# Request path

- API {#api type=service x=100 y=120}
- Database {#db type=database x=500 y=120}

## Flows
- api -> db {#requests label="requests" color=#f05a47 speed=1 direction=forward}

Change a label to describe your system. Keep the identifiers the same when you want existing connections to keep referring to those nodes.

Check your work

Expected outcomeYou keep a portable backup and can reopen an owned server copy after publishing.

Next steps

Try the workflow in the editor, then use the reference for control details and model syntax.

Open the example or setup page Detailed reference

If a step does not work, keep an export of your model and follow the troubleshooting guide. Include the error message when contacting support, without sharing credentials or private architecture.