73 results found
-
New version sets Title to the filename
In Versions and History, when I add a new version, the Title is set to the uploaded filename. My request is to keep the same Title as the previous version.
3 votes -
The folder library display
The FOLDER view ( list- grid or category) does not meet our expectations, as it remains poorly organised. We are looking for a simple structure:
1st page: Main folders (e.g. ESCARDIO, CONGRESS, etc.)
2nd page: First-level subfolders
3rd page: Additional subfolder levelsAnd so on
In the suggested view, everything appears mixed together, which makes it difficult for us to work efficiently.
We really need a basic hierarchical structure, similar to the folder organisation in Microsoft systems.3 votes -
Add permission-based control for the “Enable search engine indexing” option when uploading or editing assets / Role-Based Control of “Enabl
- Problem Statement Currently, all users who can upload images to the DAM—regardless of their role—are able to toggle the checkbox “Enable search engine indexing” on an asset. This creates a governance and security risk because:
Some images are intended for public-facing websites and should be indexable.
Other images are intended strictly for intranet use and must never be indexed by search engines.Because all roles can toggle this setting, users who do not understand the implications may unintentionally expose internal assets to external search engines, or hide assets that should be indexable.
Today, even low permission users can make indexing…4 votes -
list view
We need "list view" in collections (and anywhere else not currently offered). This would make large collections much easier to review, avoid consistent file name truncation, and streamline UX.
2 votes -
Image preview is not large enough
When you click on an images to view a larger version it is not large enough to see the details and you can't click to the next photo from this view so you have to close the view and then it takes you back to the top of the list.
This is critical to our workflow as we need to review the files in order to make selects to create collections.
2 votes -
Naming conventions
Presets and naming - Administrator can define presets; editors select presets when uploading/downloading assets; consistent naming and rules.
2 votes -
Free text/number fields do not show in the filtering panel in DAM
Note from Rob Driscoll in https://optimizely-ext.atlassian.net/browse/DAM-4268 - "Free text/number fields do not show in the filtering panel. Will need a feature request to support that."
5 votes -
upload
Improve clarity and prevent user mistakes by redesigning how actions such as “Apply” and “Done” work and are presented in the Upload asset interface. Today, the interface gives mixed signals:
- Apply appears to save metadata but then clears the fields, causing confusion.
- "Done" actually performs the upload, but this is not communicated clearly.
As a result, users believe changes are saved, but the image can disappear without warning.
Our proposal is to:
- Clarify button labels and functions (e.g., replace “Done” with “Upload” or “Save & Close”).
- Ensure metadata fields do not reset unexpectedly.
- Provide clear confirmation messages and warnings before…
3 votes -
Set Focal Point by API
Allow focal point to be configured by API
Currently it can only be set from the CMP UI which makes an API call to
PUT https://cmp.optimizely.com/api/v3/library/image/<id> with the body:
{ "focal_point": { "x": <value>, "y": <value> } }
The DAM API endpoint https://docs.developers.optimizely.com/content-marketing-platform/reference/patch_images-id should allow us to send this as well.
7 votes -
Enable thumbnail generation for large TIFF/high‑resolution images exceeding current processing limits
Problem Statement:
When uploading large TIF or high‑resolution print‑quality assets (typically >200 MB), the CMP/DAM fails to generate thumbnails. Instead, users see a broken image icon. Optimizely has confirmed that thumbnails cannot be generated due to internal processing limitations related to file size.
This causes significant usability issues, as CMP/DAM users rely heavily on thumbnails—not filenames—to identify and select assets.- Desired Outcome / Feature Description We request support for generating thumbnails for large TIFF and high‑resolution images, regardless of original file size, through one of the following approaches (implementation method left to Optimizely):
The core requirement: All uploaded assets must…
3 votes -
Enable Drag-and-Drop Folder Navigation and Asset Relocation After Bulk Upload
When users perform a bulk upload of assets into the DAM, they typically upload all files into a single, temporary folder (e.g., “Bulk Upload”). Afterward, users need to organize these assets into their proper folders within the DAM catalog structure.
Currently, the process requires opening multiple folders and manually moving each file, which is time-consuming and inefficient, especially when dealing with large batches of assets.
Users need an intuitive and efficient way to organize assets after bulk upload. This should include:
1)The ability to see the folder structure as a tree view in the DAM interface.
2)The ability to drag…
6 votes -
DAM Asset Reference in VB
I'm looking to enable linking a Link-type property to DAM assets (e.g., PDFs, images, and other media files).
I have two concerns:
1. LinkItem is not a ContentReference, but Link fields can still link to internal Pages and Media, both from CMS and DAM. Why would a .pdf DAM asset be treated differently?
2. If DAM only supports ContentReference / ContentReferenceList, then we need two separate fields in one block:
• Link field for URLs / Pages
• ContentReference field for DAM assets to get PDF links from DAM
This creates duplicate fields and may confuse editors.Is there any…
1 vote -
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.5 votes -
Consent / model approval on assets
Consent / model approvals is something we get asked from a lot of customers. Every competitor have this. The customer want to select assets in the DAM and send for approval directly to the person/model via email/sms. The consent is then linked as a file and/or set as metadata. Notifications should be sent out before consent is expiring.
2 votes -
AI facial recognition
When uploading a new image, it should be automatically linked to images in the DAM where the same person appears. Most competitors have this and is requested often.
2 votes -
When I rotate an image, I need to tick a box and swap the height and width value to prevent letter box lines from appearing in the new image
I am trying to rotate and image within the image library but bars appear at the top and bottom of the image when I do, after the image has saved. When I contacted support, I was told that I need to follow these steps.
1. Rotate the image
2. Uncheck the Keep Resolution checkbox
3. Swap the width and height values in the Crop Size inputIn any other image editing software I have ever used, I just click a Rotate button, this seems like a big step backwards in usability.
The attached image shows an image which was rotated…
1 vote -
Native in-"Optimizely CMS" asset picker for DAM — no new window
Problem: Selecting a DAM asset from a content property in CMS opens a new browser window and moves the editor into the standalone DAM UI. Optimizely Support confirmed this is current expected behavior with no planned change.
Impact: Editors lose context on every image pick, juggle multiple windows, and get an inconsistent experience versus the inline local Media selector. It actively discourages DAM adoption.
Request: Bring DAM asset selection inline into CMS — same modal/pane style as the local Media picker — so editors never leave the CMS window to pick an asset.
1 vote -
file size max?
I recently received a collection of decks from the Roadshow. One was larger and instead of opening, it pushed me to Google Slides.
This is unacceptable.
File name was: -NYC Roadshow- Experimentation Agents in Action From idea to insight.pptx
1 vote -
truncated file names
Thumbnail view settings should offer 1, 2, 3 row file name layouts to avoid truncation.
1 vote -
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.
5 votes
- Don't see your idea?