Recoverable states on compatible changes
Preserve earlier content when supported saves or updates modify a managed Cloud item.
Capability
Versions and restoration
Review Cloud item history, download previous versions and restore content safely.
Overview
Review Cloud item history, download previous versions and restore content safely.
Recoverable states on compatible changes
Preserve earlier content when supported saves or updates modify a managed Cloud item.
History attached to one resource
Keep revisions connected to the same item code, properties, permissions and surrounding workflow.
Revision context before acting
Use available date, author, size and state information to identify the version you actually need.
Features
What Versions and restoration can do
History attached to one resource
Keep revisions connected to the same item code, properties, permissions and surrounding workflow.
Revision context before acting
Use available date, author, size and state information to identify the version you actually need.
Previous-version download
Retrieve an earlier file for inspection or comparison without making it the active content.
In-place restoration
Return the active item to a selected state without manually replacing files or changing its identity.
Retention and quota control
Apply account rules to how many revisions remain recoverable and how their storage is accounted for.
Version and recycle-bin recovery
Recover earlier content through versions and recover removed items through the recycle bin as two distinct safeguards.
Events for integrated workflows
Use version-created and version-restored events to keep external processes informed of important content changes.
Recovery path
Inspect first, restore only when needed
Earlier states stay connected to the active item so recovery is deliberate and traceable.
-
01 Save a change
A compatible update preserves the previous content as a managed revision.
-
02 Review history
Use revision context to identify the state that may be required.
-
03 Inspect or download
Retrieve previous content for comparison without changing the active item.
-
04 Restore in place
Make the selected state active while preserving the resource identity and access context.
Operational detail
How Versions and restoration works in practice
Version history protects editable work by keeping recoverable states tied to the same Cloud item, instead of relying on manually renamed copies spread across folders.
History attached to the item
Previous states remain connected to the resource code, properties and permissions, keeping the evolution of one item in a single place.
Changes create recoverable states
Compatible saves and updates preserve earlier content according to the versioning and retention rules applied to the account.
Identify the required revision
Dates, user context, size and other available metadata help distinguish revisions before downloading or restoring one.
Restore without manual replacement
Select an earlier state from the version panel and return the active item to that content while preserving the managed workflow.
Retention remains controlled
The number and lifetime of recoverable states can depend on account policy, storage limits and cleanup rules.
Versions and recycle bin complement each other
Versions recover earlier content; the recycle bin recovers an item that was removed from the active Cloud listing.
Frequently asked questions
Questions about Versions and restoration
No. Restoration acts on the existing Cloud item, so its identity and surrounding properties remain associated with it.
Yes. When download is available, a previous state can be inspected or downloaded before deciding whether it should become active again.
Not necessarily. Retention depends on account policy, storage limits and configured cleanup rules.
No. The recycle bin handles deleted items, while version history handles earlier content states of an item that still exists.