534 results found
-
Cross-Instance Asset Sharing & Synchronization
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.
- Share assets across instances through a secure "Share to Instance" action.
- Option to synchronize assets automatically, ensuring updates and new versions are reflected across connected instances.
- Preserve metadata, taxonomy mappings, permissions, renditions, and usage rights during transfer.
- Allow users to reference a source asset without duplicating files, creating a "single source of truth" across instances.
- Support sharing assets directly within CMP workflows, work requests, campaigns, and approvals.
- Provide administrator controls to define…
11 votes -
Spike Smart Duration + Sequential Due Date Issue with Due Dates going to the past or going out of order
When a user completes a step on a Task made using a template, the Step Due Date is updating to a past date. This is causing the cascading update to Smart Duration. The original issue was thought to be that the Smart Duration is working as expected. But its really the first date being on a wrong date that is causing the whole problem. On the screenshot attached, notice how an action taken on June 12 is making the Due Date shift to June 9th automatically. Which should not happen.
- Due Dates should not update just because of completion of…
13 votes -
Should be able to recover deleted campaigns from recycle bin
Being able to recover campaigns, not just tasks, from the recycle bin is a must-have for a work management system. We had an experience that showed how risky it is when that option isn’t available, especially when important campaigns are at stake and can be deleted by mistake. We hope that this a supported feature is on the product roadmap.
19 votes -
Conditional / Dependent Fields in CMP & DAM
We would like to see support for dependent fields across CMP objects — specifically Tasks, Campaigns, Work Requests, and Assets. The core need is for one field's value to dynamically control the behaviour of another field on the same form.
Core Use Cases
- Show/Hide Fields: Selecting "Requires Translation? → Yes" automatically reveals a hidden "Target Languages" field. If "No", the form stays clean and hidden.
- Make Fields Required: Selecting" Is Paid Media? → Yes "dynamically forces an "Approved Budget" field to become required before the user can proceed.
10 votes -
Duplicate a step (including substeps) in a Workflow
Duplicate a step (including substeps) in a Workflow. When I need to add another review, it would be nice to copy the previous review step with all of its substeps in the existing Workflow.
25 votes -
Set up recurring tasks once that creates separate tasks based on the frequency
We have weekly, monthly, annual and bi-weekly tasks that need set up. Currently, I have to set up 52 tasks per weekly task, etc. It would be nice to set up one weekly task with a start date/end date and frequency so that Optimizely creates separate tasks for said frequency instead of manually creating separate tasks.
15 votes -
Tab/Section For Final Campaign Results
We need to configure a centralized Post-Campaign Results section within our campaign workflows to standardize how we report on performance. More specifically, we require custom fields or a dedicated analytical format that allows team members to input final data points such as overall social engagement metrics, webinar attendee/conversion stats, paid digital performance, and total leads generated. The goal is to move away from spreadsheets and move into Optimizely to ensure that every completed campaign has a structured, searchable record of its impact directly within the platform for future benchmarking.
13 votes -
Add a “Requests by Assignee” view to dashboards
Add a “Requests by Assignee” view to dashboards, showing who is assigned or approving each request, rather than who raised it. This helps track ownership and progress more effectively.
16 votes -
Need a new role with less access than Super Admin to provision new users
We want to provide our internal IT Support team that manages provisioning of new user account and access setups with just enough access to create and manage user accounts in CMP, but the only current role that would meet this requirement is Super Admin, which provides way too much additional access.
6 votes -
Improve reporting on Social Publishing
We want reporting on the impact of social posts, similar to sprout social so that we can leverage CMP directly for this purpose: Video views. Competitor engagement. audience growth. Paid vs organic performance. Post performance.
7 votes -
Add downstream dependencies to the Related activities linked within a task
Currently, the Related tab allows us to link tasks that the current task depends on (upstream dependencies). However, there is no way to link or view tasks that are dependent on the current task (downstream dependencies).
We would like to see an additional relationship type, such as "Blocks" (or similar naming), that allows users to designate tasks that cannot begin until the current task is completed.
This enhancement would provide a complete view of task dependencies by enabling users to see at a glance:
Depends On: Tasks that block the current task from starting.
Blocks: Tasks that are blocked by…6 votes -
Once a workflow is created and an existing asset has been added allowing that asset to retain it's meta data instead of replacing it.
At the moment if an existing asset is added to a task where a workflow is already added the fields within that existing asset are blanked and whatever is in the task fields are used. This is regardless of if you toggle not to inherit fields from the task.
We'd like to be able to keep the metadata in the fields of an existing asset and for it to be used at task level when added.
10 votes -
Filtering Options in the DAM
Two different ideas for filtering in the DAM
1. Just field group
2. Recommended set of filters with the others being hidden (i.e., not having to chage the filters every time12 votes -
Requirement to select more than 100 assets at a time in the DAM
It would be great if you can select more than 100 assets at a time in order to be able to edit in bulk.
12 votes -
Re-assign Campaign and Tasks when Users are Removed
When Users are deleted from the platform on leaving the team (or business), all Assets, Tasks and Campaigns are orphaned, and there is no way to bulk view or assign them - you have to go into each one individually and re-assign it.
As there is no ability for Assets, Tasks or Campaigns to be owned by Teams and not individuals, and we have certain Users who own thousands of Assets, this is a potential massive headache in the event this user leaves, or changes roles.Please introduce better tools for re-assigning ownership of items as opposed to everything having…
7 votes -
Enable editing of key fields directly within the Plan module, including fields such as Depends On, Status, and Cur
Currently, these fields cannot be edited inline and require opening each individual item. This slows down workflow management and makes bulk updates or quick adjustments inefficient. Allowing inline editing would improve usability, speed up resourcing and timeline changes, and reduce administrative effort when managing multiple tasks.
12 votes -
Add step assignees and step due dates to Plan > Board view CSV export
We're looking for a CSV export that contains the following information:
campaign name, task name, step name, step assignee, step due date.In Plan > Board view, each card shows you all that information, but the CSV export of that view doesn't contain step assignee or step due date.
We'd like the CSV functionality to be enhanced to include step assignee and step due date which will help us with content ops reporting.
8 votes -
Bulk Replace Existing Images Without Creating Duplicates
Current Limitation: When a user uploads a replacement image with the same file name or identifier, Optimizely creates a new, separate asset rather than replacing the existing one. While version control exists for individual assets, there is no bulk version-replacement workflow.
Use Case: In industries like retail, manufacturing, and consumer goods, suppliers regularly update product packaging while keeping the same SKU and naming convention. When these updated images need to be loaded into the DAM, the platform creates duplicate assets instead of recognizing them as replacements. Users are then forced to manually identify and delete the old versions — a…6 votes -
Auto-Attach Metadata Fields at the Moment of Upload
Current Limitation: When uploading assets to the DAM, users must manually add and populate metadata fields after the upload is complete. There is no ability to pre-configure or auto-attach specific fields during the upload process, and required fields cannot be scoped to specific folders or asset types — they apply globally or not at all.
Use Case: Many organizations rely on specific metadata fields to drive downstream integrations (e.g., web publishing, POS delivery, SFTP triggers). During mass uploads, users frequently forget to attach these fields or spend significant time manually adding them post-upload. This creates incomplete metadata, delays integration workflows,…6 votes -
Increase Bulk Upload Limit Beyond 200 Assets
Current Limitation: The DAM UI caps upload at 200 assets per session.
Use Case: Teams that manage high-volume asset libraries — such as retail, eCommerce, or manufacturing — regularly need to upload thousands of images at a time (e.g., new vendor catalogues, seasonal refreshes, or platform migrations). At 200 assets per session, uploading large batches becomes a time-consuming, repetitive process with limited progress visibility. The current workaround of using SFTP or API-based ingestion requires technical resources and additional configuration, making it inaccessible to everyday business users.
Requested Enhancement: Increase the UI upload limit to at least 1,000 assets per session,…6 votes
- Don't see your idea?