104 results found
-
Show file extension on list and gallery view and Filter by extension
We would like to filter by extension and also have the ability to see the extension on the list view.
Ability to expand the file name Column so you can see the file extension. (see attached) or have a column for extension.
Ability to filter by extension just like you can filter by File formatUse case someone is looking for a specific logo in SVG format. Right now they have to hover over each asset to see the extensions.
2 votes -
Filtering ability in DAM on mobile
There is no filtering functionality when accessing the DAM via mobile - can this be added please
1 vote -
DAM Filter Configuration Customization
The default arrangement of filters in the DAM causes confusion for users, as irrelevant filters appear at the top and cannot be removed or reordered, which may impact user efficiency. A solve for this would be to allow each account super admin the ability to customize their filter order in the platform.
2 votes -
Create folder/asset should be two separate options on setting roles in the DAM
When creating roles for DAM using it would be more beneficial is create folder/asset were two options not amalgamated into one
1 vote -
Warning if all mandatory fields and due date are not complete
It would be good if when uploading an asset, if the due date or the mandatory fields were not complete there was a warning sign rather than the asset simply not uploading
1 vote -
Native in-"Optimizely CMS" asset picker for DAM — no new window
Problem: Selecting a DAM asset from a content property in CMS opens a new browser window and moves the editor into the standalone DAM UI. Optimizely Support confirmed this is current expected behavior with no planned change.
Impact: Editors lose context on every image pick, juggle multiple windows, and get an inconsistent experience versus the inline local Media selector. It actively discourages DAM adoption.
Request: Bring DAM asset selection inline into CMS — same modal/pane style as the local Media picker — so editors never leave the CMS window to pick an asset.
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…
5 votes -
Preserve Folder Structure When Uploading Folders to DAM
Problem:
When uploading photography to the DAM, photos that are already organized into folders and sub-folders on my computer do not retain that folder structure when uploaded as a batch. Instead, the files are uploaded as one large, unorganized collection.For example, uploading a folder containing 300+ photos across multiple sub-folders results in all of the images being placed together rather than maintaining the existing organization.
Current workaround:
I have to manually re-create the folder and sub-folder structure within Optimizely and then upload the photos into each corresponding folder. With a large number of files, this is extremely time-consuming.Feature…
1 vote -
Generation
When uploading EXR + FIG file types creat a preview/thumbnail for the within the DAM. This causes significant usability issues, as CMP/DAM users rely heavily on thumbnails—not filenames—to identify and select assets.
1 vote -
turn off visibility to nested assets/folders that are restricted through permissions to the parent folder
Currently if an asset with global visibility is nested within a folder that is restricted, then the asset is shown at the root level. A toggle to change this would be great so that assets no longer show at the root when they are nested within a folder that's been restricted.
2 votes -
Bulk Download Public URL's
We need to bulk download public URLs to share with our partners and to plug into our Product Information Management system. Pulling them one by one is not feasible for the number of items we have.
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…
10 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…
24 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 -
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.
9 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.
-
Sharing Assets Across Instances
Organizations (like mine) often operate multiple DAM and CMP instances across business units, brands, regions, or subsidiaries. Today, sharing assets between instances requires manual downloads, re-uploads, duplicate storage, or granting users access to multiple environments. This creates inefficiencies, version control risks, governance challenges, and duplicated effort.
Suggestion is to introduce a native Cross-Instance Asset Sharing & Synchronization capability that allows users to securely share, reference, or synchronize assets between DAM/CMP instances without requiring manual downloads and uploads.
Key Capabilities
- Share assets across instances through a secure "Share to Instance" action.
- Option to synchronize assets automatically, ensuring updates and new versions…
1 vote -
Dynamic Metadata & User Attribute-Based Permission Model
Beaulieu manages a large volume of digital assets across multiple brands, business units, regions, markets and customer types.
As part of our DAM strategy, we are evaluating Optimizely DAM as a replacement for our current Wedia DAM. However, one of the key capabilities preventing us from migrating is the lack of a flexible permission model based on both asset metadata and user attributes.
To successfully support our governance model, we require a permission framework where access is determined dynamically by matching asset metadata (tags) with user attributes (roles, groups and tags). This approach enables scalable governance, minimizes manual administration and…
1 vote -
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
- Don't see your idea?