When adding a new version, you'll be prompted to upload a new file. This will become the new final version of the asset.
Metadata is tied to versions. Currently, you can only edit metadata on the Asset Details page, not the Asset Digest. So for example, if you make edits to the metadata on the Asset Details page for Version 2, you will see those edits reflected in the metadata in the Asset Digest when Version 2 is saved as final – but not for Version 1.
Note that if you are switching between versions in the Asset Digest, refresh the page to see current metadata for that version.
From the Asset Details page, click the Add Version button. Any file uploaded using the Add Version button is added as the most recent version.
Versions cannot be deleted, but they can be hidden on the Asset Details page if a prior version should no longer be visible, but other versions should. Click Hide Version to remove a version from view. Note that once a version is hidden, it cannot be unhidden. Hidden versions count towards storage space in the DAM.
To view or manage asset versions, users need specific permissions.
Asset Digest
Edit assets metadata, type, and preview: Required to upload new versions and save final versions.
Access asset versions: Required to view previous versions.
Delete assets: Required to delete versions in Asset Digest.
Asset Details
Access asset versions: Required to view non-finalized versions.
Edit assets metadata, type, and preview: Required to finalize and archive versions, and to create assets from versions.
To add a new version, users need at least one of the following permissions:
Add assets
Remove assets
Expire assets
Release assets
Edit assets metadata, type, and preview
When adding new versions, the filename of the new version does not need to match the old versions, and conflict resolution isn't needed. The existing filename is not overwritten with the newly uploaded filename, but you can edit that in the metadata.
Users without the Access Asset Versions permission only see the finalized version of the asset. This ensures they access the most current and approved version. Set a version as Finalized to update the share link and embed code to reflect the latest version and maintain consistency in asset distribution.
After you add a new version of an asset and set it as finalized, it will take approximately one hour for the new version to appear in share links, embed codes, and portals. Our delivery network has an hour-long time-to-live cache and that needs to clear before new versions appear.
If links are needed immediately for critical information or urgent timing, upload the asset as a new asset rather than using the versioning feature.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
To add a new version, users need at least one of the following permissions:
Add assets
Remove assets
Expire assets
Release assets
Edit assets metadata, type, and preview
When adding new versions, the filename of the new version does not need to match the old versions, and conflict resolution isn't needed. The existing filename is not overwritten with the newly uploaded filename, but you can edit that in the metadata.
Users without the Access Asset Versions permission only see the finalized version of the asset. This ensures they access the most current and approved version. Set a version as Finalized to update the share link and embed code to reflect the latest version and maintain consistency in asset distribution.
After you add a new version of an asset and set it as finalized, it will take approximately one hour for the new version to appear in share links, embed codes, and portals. Our delivery network has an hour-long time-to-live cache and that needs to clear before new versions appear.
If links are needed immediately for critical information or urgent timing, upload the asset as a new asset rather than using the versioning feature.
If this content did not answer your questions, try searching or contacting our support team for further assistance.