Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary:   Use-case: We have built a taxonomy in our AEM DAM based on custom fields for search, filtering and reporting. We are using a namespace to bucket all of these tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. The first level of those tags is a category which pairs up to a custom field used for search. These tags are technically "buckets" as well. We would like to set these up as namespaces as well but have them be children of the overarching namespace for our organization? So the structure would look like this:organization-namespace:category:tag-level-1/tag-level-2 Current/Experienced Behavior: We have a namespace to bucket all of our custom tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. However, the first level of those tags is a category which pairs up to a custom field used for search. Improved/Expected Behavio

Request for Feature Enhancement (RFE) Summary: Sonar ruleset significantly influence BMW's development workflows. To ensure smooth integration and minimal disruption, it is essential that any changes to these rules—including minor adjustments—are communicated in advance. Developer teams require early access to updated rule definitions so they can validate their code against them before the changes are enforced in Cloud Manager pipelines. Use-case: BMW experienced a situation where a previously successful pipeline began failing overnight due to newly detected Sonar vulnerabilities, despite being based on the same commit. This indicates that the Sonar ruleset had changed unexpectedly from one day to the next. Given BMW’s multi-project setup—comprising around 10 interdependent projects managed by different development teams—each project is built through its own pipeline. As a result, a Sonar scan failure in any one pipeline can have a significant ripple effect across the entire deve

Request for Feature Enhancement (RFE) Summary: I would like to see more of a separation in how assets and folders are managed in AEM. They are both managed the same way in 2 separate spaces, the assets pane and teh content tree. I would like to see the content tree be the space for managing folders and the assets pane be the space to manage assets. Use-case: Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. In this use case we'll use brands and lines of business. We have assets that are are for a specific brand Current/Experienced Behavior: Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. There are folder based profiles added to those folders including tags that are applied to any assets added to those. We also created a workflow that will copy tags down from parent to child so those tags aren't overridden by subfolder tagging.   In this use ca

Request for Feature Enhancement (RFE) Summary: Add option to sort by page navigation sorting for path/link chooser components. additionally to sort by alphabet.Page structure should follow the site's navigation hierarchy consistently — both in the Sites panel and when selecting internal links within components. The current alphabetical sorting in link dialogs should be replaced with the same hierarchical order used for page editing.Acceptance CriteriaPage structure follows navigation hierarchy across all AEM interfacesApplies to all linkable components (e.g., teaser, button)Same page order as in the Sites panel Use-case: Selecting a path to a Page Current/Experienced Behavior: pathlist is sorted by alphabet Improved/Expected Behavior: sorting can be selected. sorting by sitestructure, maybee sorting by any other criteria Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Sanitas Screenshot (if app

Request for Feature Enhancement (RFE) Summary: When working in smaller or half-screen viewports in AEM, key page actions such as Delete and Move become hidden within the “more actions” (three dots) menu, often requiring scrolling to the very bottom to locate them. Maybee show only Icons and remove the text. Save some space. Show the text with hover effect. Use-case: ContentManager want to work fast Current/Experienced Behavior: Button is hidden Improved/Expected Behavior: Button should be visible Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Sanitas Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently, unpublishing a page requires using Manage Publication, which is useful for scheduling but slow for immediate removals. Adding a Quick Unpublish button, similar to Quick Publish, would allow fast unpublishing while keeping Manage Publication for advanced options. Use-case: ContentManagers want to work fast. Current/Experienced Behavior: Unpublish a page needs multiple navigation steps Improved/Expected Behavior: Unpublish should be faster by having a button for it in reach. Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Sanitas Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The inability to tag a group (e.g. “user group”) in the new CF editor comments appears to be a known limitation based on the current design of the tagging functionality. Use-case: Our business uses the comments feature to review and approve. we have use case where we have a lot of user working at the same time.  Current/Experienced Behavior: We can tag a user, or user's not a group Improved/Expected Behavior: we need ability to tag a IMS group or AEM group  Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud New Editor Customer-name/Organization name: JNJ Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The CF picker that was in the old CF editor is not available in the new CF editor, so I would like it to be added. Use-case: A modal can be launched to allow category and product selection. Current/Experienced Behavior: The new CF editor does not have a CF picker. Improved/Expected Behavior: The new CF editor has a CF picker. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 2025.7.21772.20250730T182007Z Customer-name/Organization name: IBM Digital Service Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: I would like the new CF editor to be able to specify the full path when specifying the link destination, just like the old CF editor. Use-case: Specify an external site in the link path. Current/Experienced Behavior: Cannot specify anything other than the content path within AEM. Improved/Expected Behavior: Full path specification possible, including external sites. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 2025.7.21772.20250730T182007Z Customer-name/Organization name: IBM Digital Service Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: In Adobe Experience Manager (AEM), when promoting a Launch back to the source page, certain page properties—such as title, description, alias, and tags—are not being promoted as expected. This behavior appears to be a limitation (or bug) in the default roll out configuration and affects both customized and fresh AEM instances (e.g., 6.5.22 with We.Retail content). Use-case: A content author creates a Launch to prepare updates for a press release page. They modify several page properties in the Launch version, including metadata and visibility settings. Upon promoting the Launch, the content updates are applied, but many of the page properties revert or are lost—leading to inconsistencies and manual rework. Current/Experienced Behavior: Current Behavior Launch promotion excludes certain page properties due to default rollout configuration. The configuration at /libs/msm/launches/rolloutconfigs/launch/contentUpdate&nb

Request for Feature Enhancement (RFE) Summary: Word doc re upload option not updating sub assets folder Use-case: When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word document. Due to this there is mismatch in the images in word document and sub assets folder.This is a priority issue and we need to resolve on urgent. Could you please check and let us know on this issue.1. Navigate to Assets console, files option2. Upload a document with some images. update metadata.3. Change the images/remove one or two images in the word document.4. Upload word document with Create Version option5. Check the sub assets folder , observe mismatch with source word document . Current/Experienced Behavior: When we are changing/removing the images from the word doc and re upload with create version option then sub assets folder is not updating with latest images used in word docume

Request for Feature Enhancement (RFE) Summary:   Use-case: ChatGPT and most AI crawlers do not support JavaScript. The Dynamic Media viewers are all built relying on JavaScript. Given the end user market is going to continue to grow and adopt the usage of AI tools as their primary source of information, Adobe should plan for the future and figure out some way to have some measure of support for AI.   If you give ChatGPT this question for this Adobe URL, then it demonstrates the issue:   I want you to evaluate one URL: https://s7d9.scene7.com/s7viewers/html5/FlyoutViewer.html?asset=Scene7SharedAssets/ImageSet-Views-Sample Is there an image on this URL? Current/Experienced Behavior:   Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: RTE support for <strong> and <em> tags Use-case: We are running an accessibility improvements project right now and our 3rd party a11y consultants reported some issues with they way RTE work.Right now RTE has an option to bolden a part of a text or to make it italic style. For that purpose it is using <b> and <i> standard HTML elements and this is perfectly fine. We have learnt that in some cases instead of these tags it is advisable to use <strong> or <em> tags as they also bring more context for a screen readers so that they can emphasise how to read that section of text.The <strong> tag is read by screen readers as an indication that the text enclosed within it carries strong importance. When a screen reader encounters a <strong> tag, it typically emphasizes the text, often by changing the tone or pitch of the voice, or by adding a pause before and after reading the text. This helps u

  Request for Feature Enhancement (RFE) Summary: When user account is created in Admin Console side, then the user gets sync up with AEM & user is shown in AEM side.In the same way, when user account is DELETED from Admin console, then that user shall be removed from AEM. Use-case: Management of user addition, user deletion from Admin Console. User addition/deletion policy shall have a clear user case in association with Admin Console. Current/Experienced Behavior: If existing user is DELETED from Admin console, then that user is shown as "enabled in AEM" & not removed from AEM. Improved/Expected Behavior: When user is created, then the user is shown in AEM side.In the same way, if existing user is DELETED from Admin console, then that user shall be removed from AEM Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud 2021.05 version Customer-name/Organization name:   Screenshot (if applicable):  

Request for Feature Enhancement (RFE) Summary: This idea proposes enhancing Adobe Experience Manager (AEM) by shifting the storage of display settings within Sites and DAM sections from browser cookies to an instance-level configuration. By managing display preferences (such as UI layouts or viewing modes) directly within the AEM instance, users can enjoy a consistent experience across devices and browsers without relying on client-side storage. This approach improves usability, eliminates cookie dependency, enhances security, and ensures compliance with stricter data privacy regulations. Use-case: Use Case: Unified Display Settings for Multi-Device Content Editors Scenario:A content author frequently switches between a desktop computer at work and a laptop at home to edit content in AEM. Currently, their preferred display settings—such as column view—are stored in browser cookies. This leads to an inconsistent user experience, as their preferences need to be manually reconfigure

Request for Feature Enhancement (RFE) Summary: Allow multiple VPN connections in AEMaaCS with automated failover Use-case: In case the configured VPN connection fails AEMaaCS should do an automatic failover to another configured VPN connection. Current/Experienced Behavior: Currently AEMaaCS allows only one single VPN connection (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/configuring-advanced-networking#vpn). Improved/Expected Behavior: It should be possible to configure a second VPN connection that is used in case the VPN connection has an issue (VPN gateway not reachable). Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: UBS AG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently, when a PDF component is added to a page, it restricts editing access to the components placed above and below it. This limitation affects user experience, especially during content updates or layout adjustments, as authors are unable to interact with adjacent elements without removing or repositioning the PDF component. Use-case:   Current/Experienced Behavior: Currently, when a PDF component is added to a page, it restricts editing access to the components placed above and below it. This limitation affects user experience, especially during content updates or layout adjustments, as users are unable to interact with adjacent elements without removing or repositioning the PDF component. Improved/Expected Behavior: • Users should be able to freely edit, move, or configure components that are placed above or below the PDF component.• The PDF component should not block or overlay adjacent component in a way that interf

Request for Feature Enhancement (RFE) Summary: Enable public share links for Collections in Content Hub, allowing dynamic updates to be reflected in the shared content. Use-case: Our client frequently shares Collections externally, including in press releases and with large audiences. They need a stable, public share link that reflects real-time changes to the Collection (e.g., adding or removing assets). This ensures consistency and avoids confusion or reputational risk. Current/Experienced Behavior: Currently, Adobe recommends selecting all assets within a Collection and sharing them via the Share Link feature. However, this link is static: any changes made to the Collection afterward (such as adding or removing assets) are not reflected in the shared link. To update the content, a new link must be generated and redistributed. Improved/Expected Behavior: Collections should be directly shareable via a public link. This link should always reflect the current state of the

Request for Feature Enhancement (RFE) Summary: Enhance filtering capabilities in Content Hub Collections to allow filtering by "Created By" (specific users, not just "me" or "anyone") and by "Creation Date". Use-case: Our client uses Collections extensively to organize and share digital assets. To efficiently manage and locate relevant Collections, they need to filter by the specific user who created a Collection and by the date it was created. This is especially important in collaborative environments with many contributors. Current/Experienced Behavior: Currently, the filtering options in Collections are limited to "Created by me" or "Created by anyone", without the ability to specify a particular user or filter by creation date. Improved/Expected Behavior: Users should be able to: Select a specific user from a list or input field to filter Collections by creator. Define a date range to narrow down the list of Collections. Environment Details (AEM version/service

Request for Feature Enhancement (RFE) Summary: Add a "Shared Links" interface in Content Hub with enhanced link management capabilities. Use-case: Users need a centralized interface to manage all their public shared links within Content Hub. This includes editing, reactivating, and searching links, as well as setting default expiration rules. These features are essential for maintaining control over public asset distribution and improving collaboration. Current/Experienced Behavior: Currently, Content Hub does not provide a dedicated interface for managing shared links (Private and Public). Users cannot view or edit their previously generated links, nor can they see links shared by others. There is no way to search/filter shared links, reactivate expired ones, or set a default expiration period. Improved/Expected Behavior: A dedicated "Shared Links" interface accessible from the Content Hub UI. At least for public shared links. Users can: Edit their own shared links (

Request for Feature Enhancement (RFE) Summary: Allow Adobe logs forward to IP-whitelsting-enabled client Splunk setups Use-case: Customer Splunk setups have HEC IP whitelisting set up; AEM logs forwarding cannot be enabled currently, according to Adobe support. Current/Experienced Behavior: AEM logs forwarding cannot be enabled currently, according to Adobe support, as the egress IPs from adobe side are dynamic Improved/Expected Behavior: Adobe can provide IP range(s) to whitelist on Customer Splunk side, allowing the logs forwarding  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: multiple clients  Screenshot (if applicable): - Code package (if applicable): -

Request for Feature Enhancement (RFE) Summary: Update page titles and labels in Manage Publication flow Use-case: When using the Manage Publication option to publish pages, when you choose to unpublish a page and go through the steps, there is still areas on the steps that says "Publish". From an editor/authoring POV this can be confusing as you want to be sure you are in the right area. Current/Experienced Behavior: Page titles and radio labels inconsistent with the action taken. "Unpublish" sitting next to "Publish" button looks disabled rather than active. Improved/Expected Behavior: Title: Manage Publication (Unpublish)Destination Label : UnpublishImprove the contrast on the selected/active button (consider not using shades of grey). Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: The University of Canterbury Screenshot (if applicable):  "Manage Publication (Publish)   Code package (if ap

Request for Feature Enhancement (RFE) Summary: Ensure that share links for collections in AEM Assets dynamically update when the collection's visibility changes from Private to Public, reflecting the new path in the DAM structure. Use-case: As a user managing digital assets in AEM, I need to share collections with external stakeholders. When a collection initially created as Private is later made Public via Collection Settings, or vice versa, the previously generated share link should remain valid and point to the updated path in the DAM structure. This ensures uninterrupted access regardless of changes in the collection's visibility status.   Most of the time, share links are distributed to hundreds of people, especially in contexts like press releases or external communications. If the collection’s visibility changes, it is not acceptable to recreate and resend a new link. The original link must remain valid, as updating it would be unm

Request for Feature Enhancement (RFE) Summary: Support for adding icons on the Tab and Accordion Item Use-case: As an author , I would need to add an icon to each tab / accordion Current/Experienced Behavior: Author can only add Tab Title or Accordion Title. Improved/Expected Behavior: A composite field support for the Panel Container so that author can choose the indivudal tab item , and also have the ability to add icons for each Tab Item / Accordion Item Environment Details (AEM version/service pack, any other specifics if applicable): AEM As Cloud latest version. Core Components latest varsion Customer-name/Organization name: -- Screenshot (if applicable): Existing  Proposed ( Looking for a composite multifield support)       Code package (if applicable):  

Hi,    Please build an out-of-the box OpenID Connect(OIDC) Authentication handler in Adobe Experience Manager(v6.5, on-premise) with an external identity provider Azure AD using the OIDC protocol.