106 results found
-
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 -
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
2 votes -
truncated file names
Thumbnail view settings should offer 1, 2, 3 row file name layouts to avoid truncation.
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.
8 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…
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 -
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.6 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.
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 -
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 -
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 -
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.
6 votes -
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…
5 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.
-
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.3 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.
3 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
5 votes -
Hide/Pin Filters
As a marketing team, we have added Fields to all our imagery and we often filter based on those Fields. In the filter section, we would like to be able to Pin the Fields that we use often and hide the filters that we don't use. At the moment, we have to constantly scroll to the bottom of the filters and add the Fields every time.
We currently don't use these fields and would like the option to hide them: File Formats, Content Model Name, Content Types, Expiry Date, Languages, Shared By, Status.
4 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
3 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
- Don't see your idea?