Versions, trash and locking

There are three separate safety nets, at three different scales.

Undo in the designer

Ctrl+Z / Ctrl+Shift+Z, or the Undo/Redo buttons in the designer header. This covers unsaved edits in the current session: adding, deleting, moving, and property changes.

Version history

Every save snapshots the schema it replaced. On the form’s page, Version history lists them with a Restore button. The designer header links straight there.

Restoring snapshots the current version first — so a restore is itself undoable. You cannot paint yourself into a corner.

Note

A brand-new form has no earlier versions yet, so the list is empty until your second save.

Trash

Deleting a form moves it to Trash rather than destroying it; restore it from there.

Deleting a form also takes its submissions out of reach — a trashed form’s data is not reachable by direct link while it sits in the trash.

Locking

Locking a form prevents changes to its schema. Use it once a form is live in the field and you do not want its identifiers moving underneath templates that reference them.