82 results found
-
DAM Forces Manual Folder-by-Folder Downloads
DAM Forces Manual Folder-by-Folder Downloads
Summary / Problem:
Users cannot download a parent folder and all of its subfolders in a single action. To download a full folder structure, users must manually open and download each subfolder one by one, making this a frequent, manual, and time-consuming task.
This limitation slows down workflows and increases the risk of incomplete downloads, especially when users need to preserve the original folder organization.
Proposed Solution:
Enable downloading at the parent folder level so that selecting "Download" on a parent folder includes all nested subfolders and assets in a single ZIP file, while preserving…
4 votes -
Filters are pre‑applied and not configurable when opening Image Picker from CMS
Problem Description
When opening the Image Picker from the CMS, CMP DAM is loaded with filters already applied by default.Specifically, the filters Images and Folders are active when the picker opens. These filters cannot be modified or deselected by the user. The only way to reach the root of the defined folder structure (which editors are expected to work within) is by clicking Clear filters.
However, the Clear filters option is barely visible and not clearly marked as an active or important control. This creates a significant UX risk, as users may not realize that filters are applied or…
3 votes -
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 -
License Overview Function
I’d like to propose a License Overview feature that would give customers better visibility and control over their licenses within DAM. Specifically, this functionality would include:
A clear overview of the types and quantities of licenses currently held
A list of users assigned to each license
A count of available (unassigned) licenses
Several of my customers have referred to this as “basic functionality” and were surprised that this level of insight isn't already available. They’ve emphasized how such a feature would significantly enhance their internal coordination and license management across teams.
Given how often this request comes up — and…
22 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 -
Global Admin Visibility Across All Folders and Assets
Admins currently can’t view all folders and assets unless they’re explicitly shared or accessed via direct URL. This limits their ability to manage the platform effectively, ensure governance, and support users.
Request: Add a global permission or “Super Admin” role that grants read access to all content across the tenant, regardless of sharing settings. This would greatly improve governance, troubleshooting, and overall administrative efficiency.
7 votesWhile we aren’t actively planning to build this right now, we recognize its value and have logged it for future review. We’re keeping an eye on related requests and will revisit this as priorities evolve. Please keep the feedback coming; it makes a real difference.
-
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 -
Face Recognition Capability for Asset Management and GDPR Compliance
We manage a large number of digital assets (images and videos) containing identifiable individuals. Under GDPR, these assets are considered personal data and require proper consent management, traceability, and the ability to identify and remove or restrict usage upon request.
Currently, there is no functionality in the DAM to automatically identify individuals within assets, which makes manual compliance checks time-consuming and prone to human error.
Functional Requirements
Automatic Detection:
The DAM should automatically identify human faces in uploaded assets (images/videos).
Detected faces should be visually highlighted and optionally labeled.
Consent Linking:
Each identified individual should be linkable to a stored…
6 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.
-
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
- Don't see your idea?