Build better products with our product team
The Problem: Displaying inactive users creates a poor user experience when trying to confirm if object is shared or not. Currently, active users are mixed alphabetically with "No Access" or inactive users, forcing our team to scroll excessively and manually click the "X" to clean up share list. This manual maintenance is a time-sink, diverting our team from their primary goal: supporting our customers.Requested Enhancements: Collapsible or Hide "No Access" View: implement a collapsible section for users with no access, similar to how inherited permissions are handled. Users should have the "choice" to expand this list via a toggle (>) only when needed. Automated Team Offboarding: way to automate the removal of inactive users from Teams. Currently we either have to have team owner go and remove or our ops team need to go into the user and X all the teams they are tied to. Again takes away from our doing our day to day jobs. The Goal: Minimize administrative overhead so our team can focus on customer-facing tasks rather than manual permission management.
I’d like to share feedback regarding the new Feeds UI, as the current default behavior is creating significant usability issues.Right now, the report suite filter defaults to a state where none of the report suites are selected. Because of this, users must manually select every report suite before they can see any feeds. For organizations with a large number of report suites, this becomes extremely time-consuming and makes the interface difficult to use.Ideally, the default behavior should either:- Show feeds for all report suites by default, or- Provide a more practical filtering option, such as filtering by active feeds.The current setup adds unnecessary steps to a workflow that used to be much more efficient and makes managing feeds considerably harder for teams with many report suites.Please consider revisiting the default filtering behavior to improve usability and reduce friction when accessing feeds.
現在、Marketoの標準機能ではSFDC同期時に発生する特定のエラーメッセージ（例：CANNOT_UPDATE_CONVERTED_LEAD など）を直接検知してトリガー（自動通知）に利用することができません。そのため、スマートキャンペーンの「実行結果」タブを定期的に手動確認するかエラー対象を個別に確認・対応するといった運用が必要となり、件数が多い場合は対応工数が大きくなっています。 以下のような機能追加をご検討いただけないでしょうか。 SFDC同期エラー内容（エラーメッセージ／エラーコード）を条件として検知できる仕組み スマートキャンペーンや通知トリガーで使用できる 特定エラー発生時に自動通知が可能になる 同期エラー対象レコードを一括抽出（エクスポート）できる機能 修正後、再アップロード（インポート）することで一括更新できる仕組み 同様の課題を抱えているユーザーも多いと考えられるため、将来の製品改善としてぜひご検討いただけますと幸いです。
We would like the ability to display specific dashboards at the project template level. Our projects are at the individual deliverable level (i.e. an individual print piece, email, web page etc.), and we have templates for the different medium types. We would like to be able to add custom dashboards that provides specific information for that particular medium type. So for the print template, we have the print dashboard, for the email template, the email dashboard, and so on. The source information for the dashboards will be from the project details, but the dashboard/reporting will allow us to highlight specific information.
Idea: Enforce required fields on custom forms and do not allow a task to be completed before they are populated. There have been several of these ideas in the past but really wanted to bring this back up in a newer idea forum as this is a huge concern coming from a highly regulated industry. I would really anticipate that this impacts almost every organization that uses Workfront as this is really expected behavior when you indicate that a field is required. Idea option 1: Required * = field must be populated before status can be moved to complete. Idea option 2: Could we potentially add an option for “Required to close” checkbox when designing a custom form field; a second required checkbox option that drives different types of required action. This would mean you could leave the current structure as is, but simply expand to enforce required nature upon the task completion trigger. Current Functionality: If a form is not opened to edit mode, the application does not review the attached forms to confirm if fields are required or populated; it simply allows a task to close. What happens if a field is not populated? Manual processing to locate missing information Bad user experience requiring rework Incomplete and untrusted data Automation potential issues from incomplete fields Audit and process issues Missing sleep due to concern that someone did not fill out a field that is absolutely required! Just me? Just like all social media content creators love to say…make sure to give this a vote, subscribe and send to everyone you know to get some momentum on this!
A portion of our end users access Workfront via iPad. While testing, I confirmed that the time field within the date field is functional; however, it requires time to be entered in an exact XX:XX AM/PM format, which creates a poor user experience on mobile devices.Given the volume of iPad users on our team, I recommend Adobe revisit the time field input to support a more intuitive editing experience, such as a scroll selector or auto-formatting, to reduce friction and improve usability across devices.
Capping Business rules in Admin section is only applied for the highest-priority identity namespace. We have few identities with our Hybrid data modal and would like an option to be align capping with the selected identity.
I wanted to suggest an improvement regarding how we handle delegated issues in Workfront. As it stands, unless a delegate user takes ownership of a project, the delegated issue will only appear in their "my work" widget. This setup isn't quite streamlined enough for our needs. Could we request to have Workfront include delegated tasks in the "my task" widget as well? This adjustment would provide a more cohesive and efficient view, allowing us to better track and manage our responsibilities. Thank you for considering this suggestion. Looking forward to your thoughts on this matter.
What do we need:Create or update a user notification option that lets assignee(s) know when a task can start work! (Can Start = True = Notification) My Ask → Please Upvote this idea! There is currently not an option for users or admins to enable a notification to be sent to a user or team that is assigned to a task that lets them know that they can start working on a task; a trigger once the Can Start indicator on a task moves to True. Users do not receive notifications that let them simply know they can start working on their task. What’s available today in user notifications? There is an option for “All predecessors of my tasks are completed” located in the Information about Work Assigned to Me section, but this does not always work and is not always accurate. This runs simply off directly associated predecessors on a task. If you manage predecessors at a parent task level, notification will not be sent to your users and affect your teams performance (e.g. Process B (parent task with multiple children tasks) cannot start until Process A is complete). This notification will trigger only if you have a predecessor assigned to a specific task and does not account for predecessor relationships managed through a parent. Scenario 1 - No Notifications SentScenario 2 - Notifications Sent but not accurate!
Field Content Request for Feature Enhancement (RFE) Summary: Allow defining custom 404 pages per specific page or directory (path) so that only the designated scopes show a tailored 404, different from the site-wide default. Use-case: When users access 404s under landing pages (LPs) or other special sections, the site owner needs to show a section-specific 404 that provides targeted guidance (e.g., relevant links, promotions, or contact paths) appropriate to that section. Current/Experienced Behavior: It is not possible to create a dedicated 404 page for a specific page or directory. All 404 responses fall back to the global default, which cannot convey section-appropriate guidance. Improved/Expected Behavior: Enable configuration to display a unique 404 page only for the specified page/directory scope, while keeping the default 404 for other areas of the site. 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: Provide a Page List block that allows filtering by a specific path × specific directory, and supports listing non-HTML items such as PDF files and external links. Use-case: Content authors need to easily create lists such as news, column, and article indexes based on specific directories, and include non-HTML items (PDF files, external URLs) within the list. Current/Experienced Behavior: 1. It is currently not possible to generate a page list filtered by a specific path × specific directory. 2. Authors cannot easily include PDF files or external links in lists such as news indexes without creating dummy pages and setting manual redirects. As a result, page lists cannot naturally contain mixed content such as pages, PDFs, and external URLs. Improved/Expected Behavior: 1. Enable authors to generate a page list by specifying a directory × tag (or equivalent filtering criteria). 2. Allow authors to add PDF files or external links to page lists with the same ease as adding standard AEM pages, without requiring dummy redirect pages. 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: Improve the Columns block so that (1) opening Column properties immediately after adding a Columns block does not cause errors, and (2) components inside Columns can be moved freely between Columns blocks or between Columns and Section containers. Use-case: During authoring, editors frequently add Columns blocks and adjust Column properties before placing content. They also often reorganize page layouts by moving components such as Text or Button between Columns, or between Columns and Section containers. Current/Experienced Behavior: 1. Immediately after adding a Columns block, opening the Column properties before adding any inner content results in an error. 2. Components placed inside a Columns block cannot be moved to another Columns block or to Section containers, limiting layout flexibility and forcing authors to recreate content manually. Improved/Expected Behavior: 1. Column properties should be accessible without error, even when no content has been placed inside Columns yet. 2. Components inside Columns should be draggable and movable across other Columns blocks or Section containers, enabling flexible and efficient layout adjustments. 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):
I am an Adobe and (now also) ai consultant in the fashion industry for over twenty years. I am absolutely stoked about Firefly boards and teach all designers i meet to work on it. There are two potential features that would make Firefly boards unbeatable. 1: The possibility to add style-guide information on a specific board or maybe a ‘project folder would be even better’. This will make Firefly boards instantly the number one ai tool for brands (not only fashion). 2: Integrated LLM of choice. I now teach designers to use their favorite llm to create detailed prompts for generating images and video on a firefly board. How nice would it be if there would be a sidebar with an integrated LLM. Even better if the user can choose their own favorite llm (please include Mistral for the European market).
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!
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
