58 results found

1. When I rotate an image, I need to tick a box and swap the height and width value to prevent letter box lines from appearing in the new image

   I am trying to rotate and image within the image library but bars appear at the top and bottom of the image when I do, after the image has saved. When I contacted support, I was told that I need to follow these steps.
   1. Rotate the image
   2. Uncheck the Keep Resolution checkbox
   3. Swap the width and height values in the Crop Size input

   In any other image editing software I have ever used, I just click a Rotate button, this seems like a big step backwards in usability.

   The attached image shows an image which was rotated without following the steps, just clicking the button, and selected so you can clearly see the bars at the top and bottom.

   I am trying to rotate and image within the image library but bars appear at the top and bottom of the image when I do, after the image has saved. When I contacted support, I was told that I need to follow these steps.
   1. Rotate the image
   2. Uncheck the Keep Resolution checkbox
   3. Swap the width and height values in the Crop Size input

   In any other image editing software I have ever used, I just click a Rotate button, this seems like a big step backwards in usability.

   The attached image shows an image which was rotated… more

   •  

   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  ·  1 comment  ·  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

2. Expose FocalPoint per Rendition in Optimizely Graph

   Optimizely CMP now supports setting a focal point on a per‑rendition basis, but this data is not currently available when querying assets via Optimizely Graph. As a result, consuming applications cannot apply the intended focal point for different rendition sizes.
   Providing this data in the Graph schema and SDK models would ensure consistent rendering behavior between CMP and downstream experiences.

   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

3. 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 destructive actions.
   • Make the flow predictable so users always understand what will happen next.

   The goal is to create a more intuitive and predictable upload experience. The attached pdf shows the identified UX-problem with comments.

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

   • 

   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

4. Searching within the DAM when adding an image in the CMS

   Business analyst / Content integrator

   We would like additional functionality to browse in the folders of the DAM to find an image. Currently we can only search images in the search bar on the name of the image.

   For now this works fine, however when we have more then 4-9 websites about kitchens live. Then the word kitchen will show a lot of the other brands mixed in the results. This will make choosing an image more error prone.

   So to make the DAM more future proof a folder selection of the brand would be great.

   Kind regards,
   Jeroen

   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

5. Extend the Optimizely CMS image property

   Extend the Optimizely CMS image property and DAM picker so that it can:

   1. Read image requirements from each instance of the CMS property (i.e. aspect ratio, min size, free/locked crop, allowed zoom/pan).
   2. Provide a cropping UI within CMS with zoom, pan, free/locked cropping and focal point awareness.
   3. Support round‑trip editing: cropping parameters are saved per usage in CMS and loaded again when reopening the dialog.
   4. Generate a real preview in the CMS using CDN URL parameters (no DAM variants needed).
   5. Maintain CMP as the single source of the master asset.

   • 

   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

6. DAM Forces Manual Folder-by-Folder Downloads

   DAM Forces Manual Folder-by-Folder Downloads

   Summary / Problem:

   Users cannot download a parent folder and all of its subfolders in a single action. To download a full folder structure, users must manually open and download each subfolder one by one, making this a frequent, manual, and time-consuming task.

   This limitation slows down workflows and increases the risk of incomplete downloads, especially when users need to preserve the original folder organization.

   Proposed Solution:

   Enable downloading at the parent folder level so that selecting "Download" on a parent folder includes all nested subfolders and assets in a single ZIP file, while preserving the original folder hierarchy.

   Business Impact / Why This Matters
   • Users often rely on folder structure to understand asset context, usage, or ownership
   • Current workarounds (collections or manual downloads) break folder hierarchy
   • Preserving hierarchy reduces rework, confusion, and asset misplacement after download
   • Aligns with standard expectations from DAM and file management tools

   DAM Forces Manual Folder-by-Folder Downloads

   Summary / Problem:

   Users cannot download a parent folder and all of its subfolders in a single action. To download a full folder structure, users must manually open and download each subfolder one by one, making this a frequent, manual, and time-consuming task.

   This limitation slows down workflows and increases the risk of incomplete downloads, especially when users need to preserve the original folder organization.

   Proposed Solution:

   Enable downloading at the parent folder level so that selecting "Download" on a parent folder includes all nested subfolders and assets in a single ZIP file, while preserving… 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

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

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

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

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

    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

11. Select assets across multiple pages/folders

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

    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

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

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

15. Switching between views consistency

    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

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

    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  ·  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. add non-mandatory fields to the uploader

    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.

    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

18. collections - Upload

    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

    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

19. collections - uploads

    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

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

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