Review and history

Review feedback explains what should change. Editing history explains what did change. Use both to keep revisions understandable.

Add a focused review comment

1. Open review for the intended work and select the target element.
2. Enter a concrete comment beside that element, such as "Align this label with the input field."
3. Finish the input or leave the field so the review's automatic save can complete.
4. Check that the comment belongs to the correct element and review round.

Use an overall comment for page-wide feedback. Create and name a new review round when you need a distinct pass, then use review history to inspect earlier rounds.

Saving feedback does not automatically apply a design change or start an AI task. Ask for a revision explicitly, then compare the result with the comment's intended outcome.

Inspect editing history

Open the history view and choose a retained operation. Its preview is read-only: inspecting or playing past operations does not replace your current page.

Use previous and next controls to inspect nearby records. History playback illustrates retained edits; it does not execute your application's business events or recreate every action from an old session.

Mark and restore a milestone

Give an important retained state a recognizable name using the history's milestone or keyframe action. These history keyframes are named edit states, not animation keyframes.

Before restoring a state, inspect the selected record and finish any pending property input or file task. Confirm the restore deliberately. In supported history workflows, restoring creates a new undoable operation and preserves the earlier timeline.

History coverage and persistence depend on the document author. A page, a style document, and another independent workspace may have separate histories; do not assume that restoring one restores the entire project.

Keep durable backups

History has bounded retention and cannot replace a project backup. Referenced external images or fonts may also change or become unavailable, so an old state may need its original resources to look the same.

Before a large revision, copy or version the complete saved project. Read Projects and saving for file and recovery boundaries.