Skip to content

DAM (Digital Asset Management)

DAM (Digital Asset Management)

Categories

109 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Request to be able to create renditions from uploaded .eps files in the DAM. Currently only supports PNG, JGP, and WEBP

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. In order for the select all option to appear, one asset needs to be selected first. Can the select all just always be available?

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow restrictions on who can upload to a particular folder - need to be able to block admins/creators from uploading to a single folder and give them view only access. Currently view only access still allows them to upload.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The filters collapse when moving from once collection to the next. It would be helpful for them to remain intact from the previous search.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. In the library, if the asset is a duplicate, it should be highlighted with a label.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Background

    Our company has identified a usability issue within the Optimizely DAM search experience related to persistent filters.

    According to current DAM behavior, filters remain active until they are manually cleared by the user. When a new search is performed, any previously applied filters continue to affect the search results. This is the expected system behavior as confirmed by Optimizely Support.

    Problem

    While technically functioning as designed, the current behavior is not intuitive for users and can easily lead to confusion.

    Users often initiate a new search expecting results across the entire DAM repository, unaware that filters from a previous…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Summary

    We would like to request the ability to exclude specific folders and their contents from appearing in search results within Optimizely Digital Asset Management (DAM).

    Current Limitation

    As confirmed by Optimizely Support, folder permissions can be used to restrict access to assets, but there is currently no way to hide folders or assets from search results for users who already have access to those folders. This means that assets can still be discovered through search even when they are intended to be hidden from regular use.

    Business Need

    Organizations often need to retain assets in DAM while preventing them…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Within the DAM, what's the difference between Document and PDF as PDF shows up within Documents which is causing confusion.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. As tags can freely be added to DAM assets, there is a risk that tags can be misspelt and currently there is no method of accessing a tag dictionary to remove or edit the tags, which are suggested.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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 format

    Use case someone is looking for a specific logo in SVG format. Right now they have to hover over each asset to see the extensions.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. We work with several files at a time. It would be great to drag over a selection of files instead of having to individually click on the files we would like to select. It would also be great that once these files are selected to be able to click on a relate button. Current "relate" process glitches and is not efficient.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?