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

# Publishing and versioning

> Save, publish, and manage versions of your pages

# Publishing and versioning

Every change you save in the page editor is recorded as a new version. This means you can work on a page over multiple sessions, keep drafts separate from what's live, and switch back to an earlier version if something goes wrong.

## Saving and publishing

Saving and publishing are two separate steps in Studio.

| Action             | What it does                                                                                   |
| ------------------ | ---------------------------------------------------------------------------------------------- |
| **Save**           | Records your changes as a new version. It does not change what visitors see on the live site.  |
| **Save & publish** | Saves your changes and immediately makes them live (available if you have publish permission). |
| **Publish**        | Once a version is saved, makes that saved version live.                                        |

When you save, you'll be asked to enter a short commit message describing what changed — this labels the version in the history.

Use **Save** to preserve work in progress without going live. When you're ready to make changes visible to candidates, use **Save & publish**, or use the separate **Publish** button to publish a version you saved earlier.

<Snippet file="publish-reminder.mdx" />

<Note>
  If you don't have publish permission, you'll only see **Save**. Your saved changes are kept as a version, and a colleague with publish permission can publish them.
</Note>

## Version history

Every time you save, a new version is created. Open the **History** button in the editor toolbar to see the full list. Each version shows when it was saved, who saved it, and its commit message.

### Switching to a previous version

<Steps>
  ### Open History

  In the page editor toolbar, click **History** to open the Version History panel.

  ### Find the version you want

  Scroll through the list to find the version you want to go back to.

  ### Switch to this version

  Click **Switch to this version** to load it into the editor as your current draft. You can then publish it, or continue editing from that point.
</Steps>

<Warning>
  Switching to a version replaces your current draft. Save your current work first if you want to keep it.
</Warning>

## Page comments

You and your team can leave comments on a page to flag sections for review, give feedback, or ask questions without changing the content itself.

Comments live in the preview toolbar — switch the preview into **Comment** mode to add and view them. Replies are threaded so conversations stay organised.

### Attaching files to comments

You can attach files directly to a comment — drop in a screenshot, a document, or a piece of content the page should use. This means customers no longer need to send content in a separate email and then add a comment separately; everything stays in one place.

Attached files are added to the [Uploads](/studio/cms/uploads) library automatically, so they are ready to use on the page straight away without downloading and re-uploading. You can preview an attachment in a modal without leaving Comment mode.

### Spotting outdated comments

If the content a comment refers to — the item, block, column, or section — has changed since the comment was left, a banner appears at the top of the thread. This lets you see at a glance that an issue may no longer be valid, or may already have been fixed by someone who edited the content but hasn't marked the comment as resolved.

From the banner you can click **View original** to see the page exactly as it was when the comment was left, then return to the latest version whenever you like. Any unsaved changes are restored when you switch back.

<Note>
  If you click **View original** and then leave that comment, the preview automatically switches back to the current version — this stops you from accidentally editing an outdated version of the page.
</Note>

## FAQs

<AccordionGroup>
  <Accordion title="I only see Save, not Save & publish.">
    You don't have publish permission. Your saved changes are kept as a version, and a colleague with publish permission can publish them.
  </Accordion>

  <Accordion title="I published something by mistake — can I undo it?">
    Yes. Open **History**, find the earlier version you want, and click **Switch to this version**, then publish it. Save any current work first, as switching replaces your draft.
  </Accordion>

  <Accordion title="Where did my team's comments go?">
    Comments live in the preview toolbar's **Comment** mode, not in the main content view. Switch the preview into Comment mode to see and reply to them.
  </Accordion>

  <Accordion title="A comment says the content has changed — what does that mean?">
    The content the comment refers to has been edited since the comment was left, so the feedback may no longer apply or may already be fixed. Use **View original** on the banner to see the page as it was, then switch back to the latest version. Once the point is dealt with, mark the comment as resolved.
  </Accordion>

  <Accordion title="Can I attach a file to a comment?">
    Yes. Attach files directly to a comment instead of emailing them separately — they're added to the [Uploads](/studio/cms/uploads) library and can be used on the page right away. You can preview an attachment in a modal without leaving Comment mode.
  </Accordion>
</AccordionGroup>

## Need help?

<Snippet file="contact-support.mdx" />

## Related articles

* [CMS glossary](/studio/cms/glossary)
* [The page editor](/studio/cms/pages/page-editor)
* [Uploads](/studio/cms/uploads)
* [Users and permissions in Studio](/studio/settings/users-and-permissions)