81 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 -
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 -
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 -
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 -
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 itself3 votesWe’re in the early stages of exploring this idea and would love to learn more from you. If this feature would make your workflow easier or solve a specific challenge, please share your context with us. Your input will help shape what we prioritize next.
-
Collections download one image and it's zipped
When looking at a collection via the public link, you can select one or more files. If you select just one file, that file is zipped. It would be preferred to download just the single file not in a zipped folder.
3 votes -
Complete Parent folder chain should auto tag when uploading an asset
We are trying to allow our staff to search for assets by country, city, community, project, building and unit. Each of these we can configure as folder and if Optimizely auto-tags each of the folder in the hierarchy with the asset it would simplify the upload process, and we can avoid creating custom fields for each of these assets as these are very specific requirements and not apply to our DAM usage as whole.
3 votes -
Adding folders in logic for saving views in the Library / DAM
Folders don't currently feature in the logic for saving a view within the Library / DAM. The logic only includes filters and saved search for the time being, but not folders.
We have checked with our Product team, and they have informed us that this should be submitted as feedback via the feedback portal. Thus, we're submitting it for Bentley Systems, Inc.
3 votes -
Featuring labels and their values in the unified filter panel by default within DAM if they are part of Saved View configuration.
If someone adds a label and choose value(s) to create Saved Views within DAM, then they should appear in the Unified Filter Panel by default instead of featuring under the "+Add Filters" section once someone selects a Saved View inside DAM.
Currently, If you click on "+Add Filters" and locate a label and it's chosen value (which is already appearing selected due to the Saved View), then clicking on the 'Done' button doesn't do anything either - it doesn't get added to the main filter panel view at all.
3 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 -
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 -
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 -
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.
2 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.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
2 votes -
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.
2 votes -
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
- Don't see your idea?