Skip to content

DAM (Digital Asset Management)

DAM (Digital Asset Management)

Categories

JUMP TO ANOTHER FORUM

46 results found

  1. There is no way to save a view when locating a collection, it defaults to created date. I preferred alphabetical for a project and had to sort each time I looked for a collection.

    2 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)
  2. 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.

    2 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. Hi there,

    Just wondering if it is possible to have .heic thumbnails showing up in the library? We currently have a folder - https://cmp.optimizely.com/cloud/library?parentFolderGuid=68f88646346011f09ed262250c4735a2&adv_groups=field_65bb1fa1a91c5f68875b6559 that we'd like to have thumbnails for the .heic files.

    Thanks,
    John

    https://support.episerver.com/hc/en-us/requests/1697146

    2 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. 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.

    1 vote

    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)
  5. 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.

    1 vote

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

    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 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

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

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

    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. Controls for admins to remove non-brand fonts, colours, templates (or at least to hide)

    1 vote

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

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

    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)
  13. 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

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

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

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

    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)
  17. 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

    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. Currently you are unable to add cache control headers to assets served from the DAM's CDN.

    Our Premium client would like a DAM admin the ability configure response headers for their org and/or adding a special query param to the asset url to request the CDN to add the cache-control response headers.

    1 vote

    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)
  19. 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.

    1 vote

    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)
  20. 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.

    1 vote

    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?