Is it true that you must save a page after editing to keep changes in AEM?

In Adobe Experience Manager (AEM), while editing content, there are certain behaviors and functionalities regarding saving changes. When you make edits to a page and leave the editing environment without saving, those changes will not be retained. However, it is important to note that in AEM, the process of saving might not always be as explicit as it seems, as some changes can be auto-saved or captured in draft forms depending on the settings and configurations in place.

The assertion that saving a page is not necessary to retain changes is rooted in the idea that AEM has features that can allow for changes to exist in an unsaved state until the user decides to commit those changes fully. Thus, the process of saving may not be universally applicable in all scenarios. Therefore, it's not strictly true that a user must always save a page after editing to keep any changes, because updates can sometimes be preserved through other mechanisms within the platform, depending on the workflow settings established for that particular project or site.

Additionally, it can vary based on user permissions, the specific configuration of the AEM instance, and whether the page is in a draft or published state. This flexibility makes the statement that saving a page is a requisite condition for all types of changes inaccurate.