# Can a live page save a new version of itself?

Some live pages can save their own changes as a new version of their file. What the Edit this page switch does, when a save is allowed, and what the conflict message means.

Some live pages can save a new version of their own file. A page that keeps a checklist or a set of notes in its own file can save each change as a new version, so the change lasts and everyone who opens the page afterwards sees it. This is different from **Saved data**, which keeps a page's list or notes without changing the page's file at all.

A page can do this only if it was built to. Bluedeer decides that when it makes the page, so an ordinary live page has no switch for it. A page that can do it shows **Edit this page** in its **Permissions** list, on the web and on the phone.

## The Edit this page switch

Select **Permissions** above the page and find **Edit this page**, with the line "Save new versions of this page as you." The switch is on by default. Switch it off to stop the page saving its own file as you. The page can still show its contents, but a save is refused until you switch it back on. Switching it off takes effect for this page only.

The switch is shown only to someone who is signed in. It is also shown to people who can open the page but not change its file, but a save from them is refused, as described below.

## When a save is allowed

A page can save a new version of its file when all of these are true:

- **You are signed in.**
- **You may change the file.** That is the case when you made the page, or when the page is shared so that you can edit it. Someone who can only open the page gets the message "Only people who can edit this file can save a new version."
- **The switch is on** for you on this page.
- **The page is the newest version.** If someone has already saved a newer version, your open copy is out of date. This also applies when you open an older version of the page from its version history, because that is not the newest one.

Each person can save at most 10 times a minute on a page. A new version larger than 2 MB is refused.

## What a saved version does

The new version becomes the newest version of the page's file in File manager, with your name against it, so it appears in **Version history**. If the file belongs to someone else, it is still saved there, and only the new version is added. The page keeps its settings, such as which apps it uses and who can see it. Other people who have the page open are told that a newer version was saved, and their open copy updates to it, unless they opened a particular older version.

## The conflict message

If someone else saved a change first, or you are looking at an older copy, your save is not made. The page then gets the message **A newer version was saved. Reload to edit it.** The page decides how to show it, so you may see the message in the page itself, or the page may simply not change.

To fix it, reload the page so you see the newest version, check what is there now, and make your change again. Nothing from the refused save is kept, so no one loses an earlier change.

## Related

- [How do live pages work?](https://support.bluedeer.ai/bluedeer/chats/live-pages.md) covers the Permissions list and the rest of a page's switches.
- [How do I see earlier versions of a file?](https://support.bluedeer.ai/bluedeer/files/file-version-history.md) shows how to find the versions a page has saved.