58 results found
-
I want to have the assets which have been uploaded into the DAM tagged by the ai
We are going live with CMP and loading all our existing Assets into the DAM, but none of the assets which are loaded using the API are being automatically tagged by AI with the contents of the images.
2 votes -
Support for renditions for .eps files
Request to be able to create renditions from uploaded .eps files in the DAM. Currently only supports PNG, JGP, and WEBP
4 votes -
Extend the Optimizely CMS image property
Extend the Optimizely CMS image property and DAM picker so that it can:
- Read image requirements from each instance of the CMS property (i.e. aspect ratio, min size, free/locked crop, allowed zoom/pan).
- Provide a cropping UI within CMS with zoom, pan, free/locked cropping and focal point awareness.
- Support round‑trip editing: cropping parameters are saved per usage in CMS and loaded again when reopening the dialog.
- Generate a real preview in the CMS using CDN URL parameters (no DAM variants needed).
- Maintain CMP as the single source of the master asset.
1 vote -
Allow assets to be cloned through the API
Allow assets to be cloned through the API.
This would support scenarios where an asset needs to be copied into the DAM as several different assets, each with distinct data in their DAM fields which makes them unique from one another.
The only way to accomplish this at the moment is to upload the file each time, which depending upon the number and size of the files, can become a significant amount of time.
1 vote -
Expire assets based on expire date field (GDPR related)
Organizations need to comply with GDPR and other data privacy regulations. Assets that are tied to consent (e.g., photos of people, campaign materials) currently require manual governance. Without automation, there is a high risk of expired or unauthorized assets remaining accessible, which can lead to compliance issues and reputational damage.
Proposed Solution:
Asset Expiry Date: Allow editors to set an expiry date on assets. After expiry, the asset is automatically unpublished/disabled and removed from search results and delivery endpoints.
Consent Linking: Enable assets to be linked to consent records (e.g., GDPR consent, model releases). If the consent expires or is…
3 votes -
Rendition selection as URL parameter
As a Solution Architect, I see how a lot of customers and prospects select assets from the DAM and it's a common use case to select a main image for a page and then want different renditions for things like page listings and teasers to that page. Currently the author would have to select a series of renditions manually. It would be much easier to be able to add the rendition name to the URL like this: https://images.cmp.optimizely.com/assets/rob?rendition=teaser
7 votesThis idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.
-
Ability to add alt text in multiple languages in DAM
We are using the CMS asset picker to select images from the CMP DAM.
Currently, the alt text can be added to assets in the DAM in one language only.
We operate in 27 languages (= 33 distinct country websites and often re-use images in the DAM across markets. As it stands, there is no easy way for us to add alt text in multiple languages to an asset.
Our product recommendation:
* Alt text field to allow a default language + multiple language translations, generated with AI and editable.
* Alt text translations to automatically pull through to the…11 votes -
Ability to adjust image with quality and image output
As a developer I am expecting the DAM public url to be able to be querried with unique endpoints to format the original image.
I expect there to be the following endpoints queries:
- Quality (?quality=85) - a 0-100 range of quality index of the image
- Format (?format=webp) - there should be a simple solution to give a output of a different format for the channel/or display of the image itself3 votesWe’re in the early stages of exploring this idea and would love to learn more from you. If this feature would make your workflow easier or solve a specific challenge, please share your context with us. Your input will help shape what we prioritize next.
-
Ability to edit video files
I am a marketing coordinator, I upload files to our DAM. I greatly appreciate the feature where we can edit images directly on the DAM. And it would be great if we can do similar editing with video files. Editing tools such as preset crops, filters, adjustment tools and being able to download short clips from the video file would be very useful.
5 votesWe’re in the early stages of exploring this idea and would love to learn more from you. If this feature would make your workflow easier or solve a specific challenge, please share your context with us. Your input will help shape what we prioritize next.
-
add non-mandatory fields to the uploader
Currently only mandatory fields can be shown during the upload function. It would be very helpful to also have not mandatory fields which can be filled already during the upload.
If you upload multiple assets it is very time consuming that you need to edit the assets afterwards once again in order to fill all the non-mandatory fields as well.2 votes -
Selecting All Assets Requires One Asset To Be Selected
In order for the select all option to appear, one asset needs to be selected first. Can the select all just always be available?
4 votes -
Related assets removal on the image level
Each image in the library includes a set of related assets with various crop formats (e.g., portrait 9:16, square 1:1, etc.). However, not all crop types are suitable for every image — some may only support landscape or portrait orientations. The system should therefore allow users to remove any related assets or crop variations that are not applicable to a specific image.
2 votes -
Make Name & Alt text mandatory fields when user uploads the asset
Currently, when users upload an asset (e.g., image, video, or document) into Optimizely DAM, they can click “Apply” and complete the upload process without filling in key metadata fields such as Name and Alt Text.
This results in inconsistent metadata, accessibility gaps, and difficulty in content management and asset retrieval. Ensure all assets uploaded to Optimizely DAM contain complete and standardized metadata by making the fields “Name” and “Alt Text” mandatory during the upload process.This change will:
Improve content accessibility and compliance with WCAG standards.
Enhance searchability and asset management within DAM.
Support brand consistency across all markets.
2 votes -
Switch user role from Admin to Creator
Act as a user (Creator) can reduce risk of human error but also allow testing what "regular" users can/can't see.
Less risk for doing Admin mistakes when using the platform as Creator. Easier to navigate, i.e. if Admin has access to 12000 assets that aren't showing for Creator, it's almost impossible to use Brand templates as Admin.
2 votes -
Create ability to duplicate collections
It would be helpful to be able to copy a collection to retain the cover photo and description and simply updating the collection name.
4 votes -
Request for Enhanced Flexibility in Asset Ownership Settings
We’d like to suggest adding more flexibility around asset ownership assignment. Currently, the person who uploads an asset is automatically set as the owner, but we want the ability to preset or designate asset owners separately. This is important because asset owners receive “request to edit” emails, and we want to prevent these notifications from going to non-admin users that might be the asset owners. Typically, users request edit access when they actually only need to download the asset, leading to unnecessary owner involvement and incorrect permission assignments. Allowing preset ownership would help streamline this process. reduce confusion and ensure…
3 votes -
Collection view filters collapse when moving between collections
The filters collapse when moving from once collection to the next. It would be helpful for them to remain intact from the previous search.
3 votes -
Switching between views consistency
When switching between List view and Grid view in the Library, the system does not retain the current page position.
Steps to Reproduce:
Navigate to the Library.
Go to a later page (e.g., page 638).
Switch the view from Grid to List (or vice versa).
Expected Result:
The system should stay on the same page (e.g., page 638) after switching views.Actual Result:
The system resets to page 1, causing the user to lose their place in the list of assets.Impact:
This significantly disrupts workflows when managing assets across multiple pages, especially for large libraries.1 vote -
Public URL for collection based on rendition
When sharing a URL based on a rendition if the user selects all and downloads the zip file, the files are not based on the rendition. The files in the zip file are the original file. The user can only get the rendition image by clicking each file and downloading them individually.
If a URL is based on a rendition, the end user should be able to download all files in that rendition and NOT the original image.
2 votes -
Collections download one image and it's zipped
When looking at a collection via the public link, you can select one or more files. If you select just one file, that file is zipped. It would be preferred to download just the single file not in a zipped folder.
3 votes
- Don't see your idea?