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

# Saving and Loading

> How Runchat saves your work, manages versions, and controls who can open your workflows

Runchat saves your work continuously as you edit. Local changes are kept in your browser, and substantive changes (adding, removing, or configuring nodes) sync to the cloud automatically.

## Creating a new Runchat

There are several ways to create a new workflow:

1. Visit [runchat.com/editor?new=true](https://runchat.com/editor?new=true) for a blank canvas
2. Click **New Workflow** from the editor menu
3. Click **New Workflow** from the dashboard

Creating a new workflow will overwrite any unsaved local changes. Save to the cloud first if you want to keep what you were working on.

## Saving to the cloud

Runchat saves your local changes whenever you make an edit on the canvas. Substantive changes (anything other than selection, position, or resize) sync to the cloud in the background. On a **Hobby** or **Pro** plan, a new version is also added to the save history when you add or remove a node.

<Info>
  If you open a Runchat created by someone outside your [team](/concepts/teams/teams), you'll be in read-only mode. Use Save As to keep a copy in your own account.
</Info>

## Save history

On Hobby and Pro plans, you can browse the save history of any Runchat from the menu in the top-left of the editor. Once you've named and saved a workflow, a new version is captured every time you add or remove a node.

* **Restore a version**: click a timestamp to replace the canvas with that earlier state
* **Describe a version**: add a description when saving so a milestone is easier to find later

## Privacy

Runchats created on **Starter** and **Hobby** plans are public by default. Anyone with the URL can open the workflow in editor view and see how it was built, which is intended to encourage learning and sharing.

To make a workflow private, click **Make Private** from the menu in the top-left of the editor. Private workflows can still be:

* Published as Apps
* Shared in libraries
* Used as Tool nodes inside other workflows

If you're on a [team](/concepts/teams/teams), the privacy setting applies to all team members with access.

<Info>
  Runchats created by **Pro** accounts are private by default. Toggling privacy on or off requires a [Runchat Pro subscription](https://runchat.com/pricing).
</Info>

## Loading a Runchat

From the [Runchat Dashboard](https://runchat.com/dashboard), hover over a workflow and click **Open** to launch it in the editor. To share a link to a workflow, copy the editor URL from your browser's address bar.

## Deleting Runchats

From the [Runchat Dashboard](https://runchat.com/dashboard), hover the workflow you want to remove and click the trash icon. To delete several at once, click them to select, then click delete from the header bar.

## Next steps

* [Libraries](/concepts/publishing/libraries): organize Runchats into folders and share with your team
* [Apps](/concepts/publishing/app-view): publish a web app backed by your workflows
* [Teams](/concepts/teams/teams): share workflows with collaborators