Build better products with our product team
Feature Request | Allow exporting DAM usage reports from Assets View and Admin interface so that users (end user or admin) can export DAM usage reports and are able to share, analyze, or archive reporting data offlineReports can be exported from: Assets View page Admin interface Export reflects: Selected time period Applied filters Upload and download metrics Supported export formats include: CSV (mandatory) XLSX (optional / nice-to-have) Export includes metadata such as: Report generation date Generated by user Exported data matches exactly what is displayed on screen.
Currently Asset reporting statistics available only in Asset View interface. Enable admin users to access DAM usage reports from the Admin interface without needing to switch views so that they can analyze assets usage across teams, brands, and regions.Admin users can access reporting from the Admin interface. Admin can view the same metrics as end users: Uploads Downloads Admin can apply all supported filters: Time period Brand, Sub-brand, Geo/OU, Agency, Adaptations, Master, Experience Admin visibility supports broader organizational scope (subject to role configuration). Reports load within acceptable performance thresholds for large data sets.
One challenge many users face across Adobe products is navigating documentation, tutorials, and community resources efficiently. Even though Adobe provides extensive documentation, finding the exact answer quickly can still require multiple searches across help pages, forums, and external tutorials.Proposed Idea:Introduce an AI Documentation Agent embedded directly within Adobe Help, product panels, and community pages.This agent could allow users to: Ask natural language questions about features or workflows Instantly search and summarize official Adobe documentation Surface relevant tutorials, guides, and community threads Walk users step-by-step through tasks directly inside the product Suggest related features users might not know exist Example Use Cases “How do I remove background noise in Premiere Pro?” “Show me how to create a gradient mesh in Illustrator.” “What’s the difference between Smart Objects and Linked Objects in Photoshop?” The AI agent could return: Direct documentation excerpts Visual step-by-step guidance Links to official tutorials or forum answers Context-aware help based on the current tool being used Benefits Faster learning curve for new users Reduced time searching through documentation Better discovery of advanced features Stronger integration between Adobe docs, tutorials, and community knowledge Given Adobe’s leadership in AI with Firefly and Sensei, an AI-powered documentation assistant would significantly improve how users learn and interact with Adobe tools.Curious if others in the community would find an integrated AI learning/help agent useful.
When a user copies a URL from within Workfront (e.g., via 'Copy URL' in the Documents folder menu), it pastes as a raw URL with no display name — exposing a long string of alphanumeric IDs that is hard to read and unprofessional when shared in tools like Slack, Outlook, or Teams.Current Behavior:Pasting a copied Workfront URL displays the full raw URL. Example:https://companynamehere.my.workfront.adobe.com/issue/11aa11a0001123456df123dfcc1e1234/documents?initialFolderID=11b01cbf00010123bb12345ac12d123dAdditionally, there is no 'Copy URL' option on project or task pages, so users have no native way to share a direct link to those objects, other than copying the raw links from the browser address bar.Desired Behavior:1. Copied Workfront URLs should carry a friendly display name on paste — such as the document name, object name + ID, or folder path + document name — similar to how Microsoft Teams handles copied links.Pasted Teams link comes with Display text2. A 'Copy URL' option should be added to the ellipses menu on project and task pages, consistent with what's already available in Documents — and ideally with the same friendly display name behavior.This would make shared links easier to read across tools, and give makes Workfront a more approachable for new users.
Within the Fields library you have columns:Name Type Instructions Display Type Active/DeactiveCurrently, there is no way to add a description column for fields. This makes it difficult to document important information about each field within the system.A description column would allow administrators and developers to include key details about a field, such as what the field represents, backend or integration-related notes, data source information, or other relevant technical context. This type of information is different from user instructions and is intended to provide internal documentation about the purpose or structure of the field.Having a dedicated description column would improve clarity, reduce confusion, and make it easier for teams to maintain and understand complex forms or datasets over time. It would serve as a central place to store field-specific metadata that is currently difficult to capture within the existing interface.
Request for Feature Enhancement (RFE) Summary: We would appreciate a capability in the Image component (including Hero/Carousel) to configure different images for desktop and mobile. Use-case: Authors set key visuals per device so that content remains legible and complete on smaller screens. Current/Experienced Behavior: It is not possible to switch images between smartphone and desktop. As a result, text in images may become unreadable on small screens, and key content can be cropped or cut off on mobile. Improved/Expected Behavior: Allow configuration of separate images for desktop and mobile. If either is not set, fall back to a common image for both. This would directly improve UX and reduce operational work, which would be very helpful. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable): Code package (if applicable):
Field Content Request for Feature Enhancement (RFE) Summary: We would be grateful for a feature to automatically retrieve the target file size and optionally display it in the link text (with an ON/OFF toggle). Use-case: When authors create links to files (e.g., PDFs), showing the file size in advance helps users make informed decisions (e.g., considering mobile data). Manual entry is time‑consuming and error‑prone. Current/Experienced Behavior: Automatic retrieval and display of file size is not available. Although displaying size improves usability (prevents unnecessary downloads and supports user decision‑making), maintaining sizes manually incurs operational cost and inconsistency risks. Improved/Expected Behavior: Automatically fetch the target file size and display it in the link text (with the ability to toggle display ON/OFF). This would stabilize operations and reduce effort—very helpful for large sites. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: It would be very helpful if updates to Image Alternative Text were reflected immediately in the editor UI even when Show Image Caption is turned ON. Use-case: While authoring an Image block, authors enter or update Image Alternative Text in the properties panel. Current/Experienced Behavior: When Show Image Caption is ON, text entered in Image Alternative Text is sometimes not reflected immediately or disappears from the editor view (it only appears after a page reload or publish). Improved/Expected Behavior: The entered alternative text is consistently and immediately reflected in the editor UI and does not disappear. This would reduce verification effort during authoring and be much appreciated. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable): Code package (if applicable):
Feature / Enhancement RequestDescription of the Requested FeatureThe Ford .com team would like direct access to the execution logs produced by the AEM maintenance tasks VersionPurge and AuditLogPurge (plus any future purge-style tasks) without having to open a support ticket every time they need verification.Current Behavior• Both purge tasks execute in a dedicated maintenance pod.• Logs are stored internally and are not surfaced through Cloud Manager’s log download UI / API.• End customers therefore have no self-service method to confirm that their configuration changes (e.g., updated purge schedule) actually ran.• Support must manually retrieve and share CSV log extracts on request. Desired BehaviorExpose the maintenance-task logs to customers via one (or a combination) of the following:• Add the log files to the list of selectable log types in Cloud Manager ("Download Logs") for each environment.• Expose them through the existing Log API endpoints.• Alternative UI or API that allows customers to query the most recent execution status (success/failure timestamp & statistics such as items purged).Business Impact• Lack of visibility creates operational risk; the customer cannot independently verify whether critical repository-cleanup jobs are actually running after every configuration deployment.• Troubleshooting requires a new support ticket each time, adding turnaround delays for the customer and extra load for Support.• Audit / compliance teams need evidence that audit logs are being purged per policy; manual ticket flow is not scalable. Support Investigation Summary (for Engineering Reference)• Confirmed with Engineering that purge tasks run in a separate pod; sample execution logs from 2025-10-10 were provided to the customer (attachments: auditlogpurge.csv, versionlogpurgelogs.csv).• Customer attempted to increase OSGi log levels but learned that does not affect these tasks.• There is no existing customer-facing log stream for these jobs; absence of entries in Author aemerror.log is expected.• Customer explicitly asked on 2025-10-14 to open an enhancement request “to make these log files accessible to us without requiring a support ticket.”References• Maintenance task docs: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maintenance• Logging docs: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/loggingRequested Next StepsPlease evaluate feasibility, scope, and timeline for surfacing these maintenance-task logs (or at minimum their execution status) to customers through Cloud Manager or another supported interface.Full investigation available here: https://aemcs-workspace.adobe.com/bot/dynamics/investigation/4772c7e9-af48-48dc-927f-9b57dfbea568
I had a specific requirement wherein when author is editing headless content, by publishing content fragment, the latest content must realtime, immediately show at clientside. Out of box cache mechanism only provided TTL based. So I combined few ways, cooking custom solution to clear graphql query cache. Explain my custom solution here. https://medium.com/@bsaravanaprakash/how-to-eagerpurge-persistedquery-cache-upon-cf-publish-8864e0419c5e
It will be great if we have in built feature in AEM assets to run PDF API services. Especially feature which has direct implication for websites. e.g. Tagged PDFs which is crucial for WCAG compliance.The way PDF API services are established, operations needs to be done in isolation via Adobe server or 3rd party service to process the PDFs. It will be great if we don’t have to leave AEM eco-system and perform these operations via workflows.
Currently, if you open properties of a user accound, the assigned groups are listed randomly, there is no order. If a user has a bunch of assigned groups, it is very hard to search for those groups. Request:Please sort them alphabetically - this would make it a lot easier!
Reference fields in CF models and in the Universal Editor’s Properties tab are fixed-width and use an odd font size in labels. The fixed width is quite limiting in the UE, it would be great to align the behaviour of reference fields with how other fields resize.A quick demo of the issue in is this video.
Hello, this is an enhancement request that the support team suggested I log here instead.I have an AEM Headless project with a decoupled Next.js frontend and components instrumented for the UE. Many components are containers that expect a certain structure of subcomponents. UE does not provide for instrumentation of such “precomposed” composite components, so all this inner substructure has to be tediously built out by authors. This is time-consuming and brings a learning curve: the authors don’t initially intuitively know which subcomponents are expected to go inside which container-type parent components.Obviously, we instrument the containers to only allow the right type of child components to be added, and in many cases a parent component only allows one specific type of child. Which is obvious to developers but not to authors, and here’s where the current behaviour of the Add (Plus) button gets in the way. If there is only one possible type of component that can be added, the Add button just adds it without showing. This gets the job done but doesn’t help the authors learn the structure of the components. We are really missing a control for this behaviour, ideally in the user profile preferences: whether or not to display single-entry options under the Add button. By knowing what will be added at the expense of an extra click, users will learn what goes inside each composite component. Being able to add precomposed container-type components with all inner structure of subcomponents built out would help a lot too. It’s much easier to remove optional elements from it then to add each tediously and wait for the remote FE project to return the refreshed preview into the UE…[I wanted to tag this post “Universal Editor” but no such tag is available — would be a good idea to add it]
In Asset Essentials, when searching for assets using keywords and/or filters, the search results do not indicate the number of results (even the approximate number), unlike the Touch UI.The concern is that users do not know how many results are returned from on the search criteria and do not know if they need to refine the criteria.It would be a great addition if the number of results is displayed when searching for assets.
The asset export metadata tool could use more customization to make the export simpler and more efficient.The properties to be exported dropdown only has 2 options: all and selective. The all selection exports all metadata properties. In our case, this results in 2000-3000+ columns in the excel sheet with the majority of them being blank. The selective option is not viable either because there are a couple hundred metadata properties we want included in the export which is too many to manually select.Since both of these options are not ideal, it would be beneficial to have some kind of in-between option, to be able to select metadata properties in bulk without having to select them individually or all at once.One solution could be to select which metadata schemas’ properties you would like exported. Also, if there was some way to save which properties were selected for a previous export, you would not have to re-select all of the properties each time time you want to export the metadata.
I’m working on an Adobe project which uses almost 40 programs in Cloud Manager. All those programs trigger some notifications for deployment approvals, deployment started etc, but I’m only interested in two programs. Due to the large amount of these notifications, I basically every time miss the ones that are important to me. It would be great if Cloud Manager would allow filtering the notifications by program.The same applies to the events which we receive via the event hook / aws event bridge (https://developer.adobe.com/experience-cloud/cloud-manager/guides/api-usage/receiving-events/). Here it isn’t that problematic since we deployed a lambda function to filter the events, but filtering more than 90% of the events sounds like wasted resources on both sides.
Add a built‑in lifecycle engine in AEM Assets that automatically manages asset retention, archival, legal holds, license expirations, and recommended repurposing based on usage, metadata, and business rules. Key capabilities:Automatic rules engine to retire, archive, restore, or delete assets by usage, age, or license terms. License & rights tracker with expiry alerts and automatic enforcement (block publish, flag usage). Legal hold mode preventing deletion or archival for specified assets/collections. Usage-driven recommendations: suggest reuse, transcoding, or promotion based on analytics and similarity. Audit trail and impact analysis showing where an asset is used (pages, campaigns, syndications). Configurable workflows and notifications for stakeholders (legal, marketing, ops). API/webhooks for integration with MAM, PIM, CMS and governance systems.Business value:Cuts storage costs by archiving unused assets automatically. Speeds audits and reduces manual governance overhead. Improves content reuse and time-to-market by surfacing repurposing opportunities.
As Adobe continues to make significant strides in optimizing Assets, particularly through the use of Dynamic Media for delivery, many product teams have begun to utilize AEM assets as a centralized repository. This allows them to host all assets and distribute them across various downstream channels for utilization. The current challenge we face is the absence of reporting capabilities. There is no out-of-the-box (OOTB) reporting mechanism available when assets are referenced across multiple channels without the Dynamic Media embed code; instead, they are accessed through direct dynamic media URLs. Furthermore, it is not always feasible to rely on the DM embed code for asset usage. Therefore, we are seeking a feature that can provide insights into the usage of any asset when it is referenced on any channel.Is this capability on Adobe’s roadmap or planned as a feature enhancement?
Current LimitationHEIC files can be uploaded and stored in AEM Assets, but:No thumbnails are generated No visual previews are available in the Assets UI Authors must download the file to view it This negatively impacts usability, discoverability, and editorial efficiency.AEM Assets should:Automatically generate thumbnails for HEIC files Generate standard preview renditions (similar to JPEG/PNG) Display HEIC previews directly in the Assets UI and picker dialogs Work out of the box in AEM as a Cloud Service Leverage existing asset processing pipelines (e.g. Dynamic Media or asset microservices) Respect existing permissions and renditions logicBusiness ValueImproved author experience: Editors can visually identify assets without downloads Operational efficiency: Faster asset selection and reduced friction in content creation Modern format support: HEIC is increasingly common on iOS devices and in creative workflows Reduced manual conversion: Avoids the need to pre-convert HEIC files outside AEMUse CaseContent teams frequently upload images directly from iPhones and modern cameras using HEIC. Without thumbnails or previews, asset selection becomes error-prone and time-consuming, especially at scale.Expected OutcomeHEIC files behave like other supported image formats in AEM Assets, including: Thumbnail visibility in asset grids Preview rendering in asset details and pickers Consistent authoring experience across image formats
The unique field validation is not functioning in the Universal Editor. Users can enter duplicate values without any checks. Unique fields are defined in the content fragment model.Expected behaviourThe system should validate that the field is unique in the Universal Editor. It should reject duplicate values. Or at least throw an error when editor add/patch this field in de CF.Actual behaviourThe system currently allows any value to be entered in the unique field without validation. Duplicate values are accepted.Steps to reproduceOpen the Universal Editor in Adobe.Navigate to the content fragment with the unique field (ID).Enter a value in the unique field.Enter the same value again in another unique field (ID).Observe that the system accepts the duplicate value.
Hi,Following this documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/detect-duplicate-assets for enabling the asset duplication detection, we are able to see a new message in the Touch UI’s inbox when the same asset has been uploaded to 2 different folders within the DAM.However, there are no new task created in the Asset Essentials’ task inboxWould it be possible to also have a new task created to the administrators in the Asset Essentials UI when duplicate assets are uploaded to the DAM?Regards,Henry
If you have a completed translation job, you can click on “Archive”. With that, the job is not displayed anymore in the UI. BUT there is also no chance to restore it - the word “Archive” indicates something completely different for the editor and this is, that he can restore it. So, currently it is same like “Delete Tile”. So, totally missleading options here.Request: Provide an option to restore archived jobs!
Description:In AEM Guides as a Cloud Service, the XML Editor toolbar allows customization through ui_config.json and extension JSON for multiple actions.However, the Insert Relationship Table (reltable) action currently does not support overriding default values for:Header Rows Rows ColumnsFor our project, we need the relationship table to be inserted with the following custom defaults:Header Rows: 0 Rows: 2 Columns: 2At present, AEM Guides always inserts a relationship table with the hard‑coded defaults:Header Rows: 0 Rows: 1 Columns: 3These values cannot be overridden through any configuration methods.Current Limitation (Confirmed by Adobe Support):The relationship table insertion dialog does not read values from ui_config.json or the extension JSON. Default row/column values are hard‑coded in the product and cannot be changed. Only standard tables/simpletables support configurable default settings as per the 2502 release updates. Therefore, configuring relationship table defaults is currently not supported.Impact on Teams / Business Need:We rely heavily on relationship tables for structured documentation. Manual adjustment of rows and columns each time is time‑consuming and error‑prone. Having the ability to set custom defaults improves authoring efficiency and consistency. This is critical for scaling content creation for multiple repositories and teams.Requested Enhancement:Please enable configuration support for Insert Relationship Table to allow overriding default values for:Header Rows Body Rows ColumnsIdeally, these should be configurable via:ui_config.json, or AEM Guides extension JSON Or a new configuration node under folder profilesThis feature would bring relationship table behavior in line with the recent enhancements made for simpletable and standard table insert dialogs.Benefit to Adobe Customers:Improves authoring productivity Ensures consistent table structures across content teams Reduces manual editing and human error Aligns functionality with other table components already supporting default customization
We recently completed our year‑end penetration testing for the application and identified a medium‑severity issue. The system does not restrict or sanitize PDF uploads that contain embedded JavaScript code. An attacker could upload a specially crafted PDF with embedded JavaScript, and if a privileged user later opens the PDF in a PDF reader, the JavaScript may execute within the reader process.As a remediation, can we block or reject PDF files that contain embedded JavaScript during upload?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
