Create a snapshot before risk
Use a snapshot before reorganizing a project, applying a large automation, or making a major connected-tool change.
Name the reason
A useful snapshot explains why it exists, such as Before client revision or Before repository migration.
Understand the scope
A snapshot may preserve LobeWork project state and references, but external provider histories and unrelated files may remain outside it.
Review before restoring
Restoring can replace newer state. Compare the snapshot date and affected areas before confirming.
Compare the snapshot date and affected areas before confirming.
Keep external backups
Snapshots support project recovery but do not replace a complete backup strategy for important source files.
NEED A GUIDED ANSWER?
Ask LobeWork about this guide.
The support assistant uses the same published guide library and will link you back to the most relevant article.
WAS THIS GUIDE HELPFUL?Help us improve the documentation.