43 results found
-
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 -
Remove or role restrict the “Request access” / “Request higher license” banner in CMP/DAM
Problem Statement:
Users in CMP/DAM are currently seeing a banner stating “You only have view rights” with a “Request” button. This banner appears even for users who:Already have higher access roles (e.g., CMP Creator)
Have not been restricted from assets
Should not be requesting higher access based on internal governanceWhen users click “Request”, no notification or approval flow appears anywhere in the admin console ( I am admin) but notifies one seemingly randomly selected admin.
Support confirmed:
- The banner cannot be disabled
- The button cannot be hidden
We find the process behind the request to be unclear.
The…
4 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 -
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…
2 votes -
Select assets across multiple pages/folders
Can’t select multiple images across multiple pages as it deselects when browsing other folders
2 votes -
Sorting
As a digital marketing coordinator, I'd like to be able to sort assets by popularity to understand which ones have been used more regularly. This will save time as there's currently a long list of assets to look through
2 votes -
library standard fields
We currently are limited with setting "Library Standard Fields" within the Library (DAM). We have a taxonomy that is made of several field groups / labels but they are manual to add them. A much better experience would be to have the ability to set our own Standard Fields to include others within our taxonomy.
4 votes -
Display Out of the Box Metadata in Column View in DAM For Auditing
Make OOB fields like "Enable Search Engine Indexing," "Description," and "Alt Text" available to add to the columns in the Library. I need to audit these fields and there are limitations on reporting. I would like to use the columns to visually audit assets as well as exporting a csv.
2 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 -
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."
3 votes -
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 -
collections - Upload
The ability to create a collection with the option to upload content, this would be more efficient for content for specific events or projects removing the complications of email or ftp/dropbox
1 vote -
collections - uploads
We have used in other DAM systems and would like to have in this one the ability to share a collection with the ability for our clients to upload to a collection. Extremely handy for event or project specific content and much easier than email file transfer or dropbox.
1 vote -
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…
4 votes -
Brand template remove non-related brand assets
Controls for admins to remove non-brand fonts, colours, templates (or at least to hide)
1 vote -
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 -
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 -
When creating the template, the Library should show the folders structure
When users create a template in Optimizely DAM and select an Element that requires choosing an asset (via the Library option), the current behavior displays all assets from Optimizely DAM in a single view.
This makes it difficult to find specific assets, especially in large repositories, as users must scroll through an unfiltered, unstructured list.
Requirement: Improve the asset selection experience by displaying the DAM root catalog structure with nested folders (as configured in Optimizely DAM) instead of showing all assets at once.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.
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
- Don't see your idea?