Manage asset versions

This guide explains how to view an asset’s version history, restore an earlier version, and upload a new version in Administration. It also covers how to update an asset that was published from a project.

Prerequisites

Before you begin, ensure you have:

  • Access to edit assets in Administration > Assets, through a group set up by your administrator. If Reversion isn’t in the asset’s actions menu, contact your administrator.

  • Assets already uploaded. To upload assets, use Upload assets.

View asset versions

Open an asset’s Manage Versions panel to review its current version and its earlier versions.

  1. Select Administration from the bottom-left navigation, then select Assets.

  2. Select the asset.

  3. Select Manage Versions in the panel on the right.

The current version appears at the top, with earlier versions listed below.

From the front-end portal, end users can view and download earlier versions, but only administrators can restore or upload versions.

Restore a previous version

From the Manage Versions panel, restore any earlier version to make it the current version. Once restored, that version is what end users see and download.

Upload a new version (re-version)

Upload a new version when an asset’s file changes, so the updated file becomes the current version.

  1. Select Administration from the bottom-left navigation, then select Assets.

  2. Find the asset.

  3. Open the asset’s menu and select Reversion.

  4. Drag in the updated file from your computer.

  5. Choose whether the change is a Major or Minor increment.

  6. Confirm the upload.

The new file becomes the current version.

Major versus minor is a judgement call that affects only the displayed version number. Use a major increment (for example, v1 to v2) for significant changes, and a minor increment (for example, v1.0 to v1.1) for small corrections.
The replacement file must come from your local computer. You cannot re-version using a file already stored on the platform; download it first, then re-upload it.

Update an asset published from a project

Publishing an asset from a project always creates a new asset in the DAM rather than versioning an existing one. There is no link between the project asset and the DAM copy, so re-publishing creates a duplicate rather than updating the original.

Re-publishing from a project does not update the existing DAM asset. It creates a duplicate.

To update an asset that was published from a project, choose one of the following:

  • Find the existing DAM copy in Administration > Assets and re-version it manually with the updated file.

  • Delete the existing DAM copy, then re-publish from the project to create a fresh asset.