52 results found

1. 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 are subject to the appropriate approval sequence, thereby maintaining control and quality.

   We would greatly appreciate your consideration of this request and any guidance you can provide on making this workflow possible.

   Thank you for your attention to this matter.

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

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminAnisul Hoque (Principal Product Manager, Optimizely) responded

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

2. Remove or role restrict the “Request access” / “Request higher license” banner in CMP/DAM

   Problem Statement:
   Users in CMP/DAM are currently seeing a banner stating “You only have view rights” with a “Request” button. This banner appears even for users who:

   Already have higher access roles (e.g., CMP Creator)
   Have not been restricted from assets
   Should not be requesting higher access based on internal governance

   When users click “Request”, no notification or approval flow appears anywhere in the admin console ( I am admin) but notifies one seemingly randomly selected admin.

   Support confirmed:

   • The banner cannot be disabled
   • The button cannot be hidden

   We find the process behind the request to be unclear.

   The "owner" of an image can be the developer/admin currently receiving the request for higher access is the developer currently bulk-uploading all of our image assets via the API.

   So to follow the reasoning above that means that he is the owner of all assets and therefore receive requests from individual users for access to individual images.

   We need the ability to choose who receive these requests without being the owner of all assets. It is not how ownership of image assets work in our company.

   Support notes that request link appear only if an asset is marked “Private,” but this does not match observed behavior since we have no images marked Private in prod.

   This creates confusion, governance issues, and a potential licensing escalation problem.

   Desired Outcome / Feature Description:
   We request the ability to fully disable or role-restrict the “Request access” banner and its associated features.
   Specifically:

   • Hide the banner globally for our CMP/DAM instances Or restrict visibility and functionality to certain roles (e.g., Admins only)
   • Prevent end users from being prompted to request higher access or licenses
   • Disable the automatic access request workflow entirely if it cannot be configured
   • Ability to configure who receives access requests—or disable requests entirely

   In short:
   End users must not see or use any “Request higher access” or “Request license” functions.

   1. Business Value / Rationale The current banner and request workflow conflict with company’s internal licensing and access rights model.

   Reasons this feature is critical:

   • License allocation is a controlled, cost-driven process involving approvals—users cannot self request upgrades.
   • The current banner triggers incorrect expectations and support tickets from thousands of users
   • Unclear process for appointing who receives the access requests, causing further confusion
   • Print and content teams work with sensitive assets where unauthorized access escalation poses security risks
   • User experience and trust in CMP/DAM is negatively affected due to misleading - UI behaviors
   • Ensures alignment with corporate governance, compliance, and licensing agreements

   Removing or restricting this banner reduces operational noise, prevents false requests, and brings CMP/DAM behavior in line with Company´s internal processes.

   We suggest the:

   • Ability to globally disable the “Request access” banner.
   • Ability to restrict visibility by user role.
   • Ability to disable the “Request” button entirely.
   • Access request workflow must become optional or configurable. If enabled, access requests must be routed to configurable owners.

   Dependencies / Related Items: Support Ticket: #1833126

   Problem Statement:
   Users in CMP/DAM are currently seeing a banner stating “You only have view rights” with a “Request” button. This banner appears even for users who:

   Already have higher access roles (e.g., CMP Creator)
   Have not been restricted from assets
   Should not be requesting higher access based on internal governance

   When users click “Request”, no notification or approval flow appears anywhere in the admin console ( I am admin) but notifies one seemingly randomly selected admin.

   Support confirmed:

   • The banner cannot be disabled
   • The button cannot be hidden

   We find the process behind the request to be unclear.

   The… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Add permission-based control for the “Enable search engine indexing” option when uploading or editing assets / Role-Based Control of “Enabl

   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 decisions that should be governed by a specific group (e.g., Admins, Creators, or DAM Managers).

   1. Desired Outcome / Feature Description We would like the ability to control visibility and editing permissions for the “Enable search engine indexing” setting based on user role. Specifically, we need:

   The option to hide the checkbox entirely for users who should not manage indexing.
   The ability to restrict this setting so that only designated roles (e.g., Admins and Creators) can view or change the indexation status.
   A configuration option at instance/tenant level to map which roles can manage indexation.

   In short:
   Only selected roles should be able to decide whether an asset becomes indexable. All other users should not see this option at all.

   1. Business Value / Rationale This feature supports security, compliance, and brand governance in environments where both public and internal-only assets coexist in the same DAM. Benefits include:

   Preventing accidental exposure of intranet or sensitive internal images to search engines
   Ensuring consistent and controlled SEO/indexing behavior for public-facing asset libraries
   Eliminating user errors by removing unnecessary decisions from non-expert users
   Supporting enterprise governance by limiting indexing decisions to authorized roles
   Reducing risk of data leakage and compliance breaches

   This aligns with common DAM best practices where search engine indexation rights are restricted, similar to publishing permissions in CMS platforms.

   We suggest the ability to configure which roles can see the “Enable search engine indexing” checkbox.
   Ability to configure which roles can edit the indexation setting.
   For users without permissions, the control must be completely hidden (not greyed out).
   Default behavior should maintain backward compatibility.

   Related support ticket: #1836823

   1. Priority & Urgency Priority: High Reason: Incorrect handling of indexation presents a data exposure risk, particularly for internal/intranet content. Role-based control is essential before onboarding more users and expanding asset usage.

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

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. library standard fields

   We currently are limited with setting "Library Standard Fields" within the Library (DAM). We have a taxonomy that is made of several field groups / labels but they are manual to add them. A much better experience would be to have the ability to set our own Standard Fields to include others within our taxonomy.

   •  

   •  

   •  

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   1. A clear overview of the types and quantities of licenses currently held

   2. A list of users assigned to each license

   3. 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 the clear value it brings from a customer experience and admin perspective — I’d like to ask whether this could be prioritized or at least considered for the product roadmap.

   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:

   1. A clear overview of the types and quantities of licenses currently held

   2. A list of users assigned to each license

   3. 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… more

   19 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Research & Design  ·  AdminAnisul Hoque (Principal Product Manager, Optimizely) responded

   This idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.

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

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Future Consideration  ·  AdminAnisul Hoque (Principal Product Manager, Optimizely) responded

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

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

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Free text/number fields do not show in the filtering panel in DAM

   Note from Rob Driscoll in https://optimizely-ext.atlassian.net/browse/DAM-4268 - "Free text/number fields do not show in the filtering panel. Will need a feature request to support that."

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

    1. 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 generate a visible thumbnail preview, even when originals are extremely large.

    1. Business Value / Rationale Our organization manages a large volume of print-ready originals (up to 6,500 assets in the upcoming migration), many of which exceed 200MB due to their use in advertising, building banners, and other large‑format production. Thumbnails are essential because:

    Users select assets visually, not by file name
    Broken thumbnails cause mis‑selections and inefficiency
    Internal stakeholders cannot validate assets without previews
    Bulk migration becomes risky and time‑consuming
    The usability of the DAM diminishes significantly for print‑focused teams

    This limitation blocks parts of our upcoming large migration and affects daily workflows for multiple teams.

    1. Impacted User Groups

    ✔ Content Editors
    ✔ DAM Managers
    ✔ Marketing Teams
    ✔ External agencies producing print material
    ✔ Brand teams working with large imagery

    1. Current Suggested Workaround from Optimizely

    Uploading a smaller, web-friendly version of every large image manually.
    This is not feasible for 6,500+ assets, and duplicating assets leads to governance and version‑control issues.

    Optimizely recently added a default placeholder icon, but this does not solve the business need for actual visual thumbnails.

    1. Dependencies / Related Items

    Upcoming asset migration of ~6,500 large print originals
    Cross-team dependency: brand, marketing, and agencies require thumbnail previews for workflows
    Related support ticket: #1815552

    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.

    1. 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… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Select assets across multiple pages/folders

    Can’t select multiple images across multiple pages as it deselects when browsing other folders

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Sorting

    As a digital marketing coordinator, I'd like to be able to sort assets by popularity to understand which ones have been used more regularly. This will save time as there's currently a long list of assets to look through

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. 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 and drop assets from one folder (e.g., Bulk Upload) to another folder directly within this tree view.

    Functional Requirements

    Folder Tree View:

    The DAM interface should display a collapsible folder tree on the left side of the screen, representing the full catalog hierarchy.

    Users should be able to expand and collapse folders to navigate easily.

    Drag & Drop Functionality:

    Users should be able to drag individual or multiple assets from one folder (e.g., Bulk Upload) and drop them into another folder within the same catalog.

    The system should support multi-selection of assets (using Shift/Ctrl + click).

    Bulk Move Confirmation:

    After dropping assets into a new folder, a confirmation message or progress indicator should appear showing move status.

    Permissions Handling:

    Users should only be able to move assets into folders where they have write access.

    If a folder is restricted, a warning message should appear.

    UI Feedback:

    The system should visually indicate valid and invalid drop targets.

    The folder tree should automatically expand when hovering over a collapsed folder during drag.

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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 consent record.

    If consent is revoked, related assets should be flagged or restricted from publication automatically.

    Search and Reporting:

    DAM users should be able to search assets containing specific individuals (based on consent ID or tag).

    Generate reports on assets with missing or expired consents.

    Asset Governance:

    Assets with unverified or expired consent should be automatically hidden or marked as restricted for use.

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Research & Design  ·  AdminAnisul Hoque (Principal Product Manager, Optimizely) responded

    This idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Allow assets to be cloned through the API

    Allow assets to be cloned through the API.

    This would support scenarios where an asset needs to be copied into the DAM as several different assets, each with distinct data in their DAM fields which makes them unique from one another.

    The only way to accomplish this at the moment is to upload the file each time, which depending upon the number and size of the files, can become a significant amount of time.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. 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 revoked, all linked assets are automatically disabled.

    Asset Removal Workflow: Expired assets are first placed in a “Disabled” state, allowing admins to review, extend expiry (if new consent is obtained), or delete permanently. Include audit logs to track expiry actions.

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

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Rendition selection as URL parameter

    As a Solution Architect, I see how a lot of customers and prospects select assets from the DAM and it's a common use case to select a main image for a page and then want different renditions for things like page listings and teasers to that page. Currently the author would have to select a series of renditions manually. It would be much easier to be able to add the rendition name to the URL like this: https://images.cmp.optimizely.com/assets/rob?rendition=teaser

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Research & Design  ·  AdminAnisul Hoque (Principal Product Manager, Optimizely) responded

    This idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.