46 results found
-
Indefinite Expiry Option for DAM Assets
Pre-condition: An expiry date is a mandatory field for any asset uploaded to the DAM.
As a CMP/DAM Administrator,
I want the ability to mark an asset as “Indefinite” when uploading it,
so that certain assets can remain active without an expiry date and are not affected by automatic expiry rules.Acceptance Criteria
Upload Behavior
When uploading an asset to the DAM, the Expiry Date field remains mandatory.
A new checkbox option labeled “Set as Indefinite” is displayed next to the Expiry Date field.
Checkbox Functionality
When the user selects “Set as Indefinite”, the system will:
Mark the asset as…
1 vote -
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 -
Approval Sequence
Hello Team,
We are seeking to implement an approval sequence for assets within our Content Management Platform (CMP). Our objective is to ensure that once content is uploaded, it undergoes a structured approval process, preventing direct uploads without oversight.
To illustrate, similar to how content updates in the PaaS platform are subjected to a configured approval workflow, we aim to establish a comparable process for assets in CMP.
It has come to our attention that this functionality is currently unavailable. We believe that enabling such a workflow would significantly enhance our content management process by ensuring that any asset updates…
5 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…
1 vote -
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…
1 vote -
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.
5 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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
1 vote -
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.
4 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…
1 vote -
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 itself2 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.
2 votes -
Browser back in library
Navigating folders isn't as intuitive as you might expect. Specifically browser back doesn't take you back up a level of the structure and instead to the page viewed before the library.
This is a fundamental usability flaw of the system behaviour not aligning with the user's mental model. As I user if I have progressed one step deeper into folders then the back button should do the reverse.
We've had many internal users report frustration with this
6 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 -
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…
1 vote
- Don't see your idea?