Build better products with our product team
Design Studio is clunky and outdated in my opinion. Images and files are incredibly difficult to reorganize because I am unable to move more than on item at a time. Get an error message every time.Would love for a more seamless experience when navigating or making adjustments to existing folders.
Description:Our organization manages user permissions centrally through groups in Azure Active Directory (Azure AD). These groups are synchronized with Adobe Experience Cloud, allowing us to efficiently allocate product and profile permissions based on group membership. However, currently, administrative roles such as Product Administrator, Profile Administrator, Support Administrator, and System Administrator can only be assigned to individual users, not to groups. This creates a challenge for organizations that rely on group-based permission management and automation.Why is this feature important to you:Managing permissions at the group level ensures consistency, security, and scalability, especially in large organizations. Assigning admin roles to groups means that when a user is added to or removed from a group in Azure AD, their corresponding admin permissions in Adobe are automatically updated. This reduces manual intervention, minimizes human error, and helps maintain compliance with internal access management policies. Without this capability, we are forced to manually update admin roles for each user, which is inefficient and error-prone.How would you like the feature to work:We would like to be able to assign all administrative roles (Product Admin, Profile Admin, Support Admin, System Admin, etc.) to groups, not just individuals, within the Adobe Admin Console. When a user is added to or removed from a group in Azure AD, and that group is synced with Adobe, the user should automatically inherit or lose the corresponding admin rights based on their group membership. This approach should mirror how product/profile permissions are currently managed via groups.Current Behaviour:At present, administrative roles in Adobe Experience Cloud can only be assigned directly to individual users. Group-based assignment of these roles is not supported, which complicates permission management for organizations using directory group synchronization.
Does your organization run programs with multiple projects? Are your project managers responsible for managing large volumes of projects at the same time? Are you looking for an efficiency win? I think most organization will say yes and could really benefit from this idea. Idea: Implement the ability to quickly and easily assign users to roles at not only the project level, but also on the program level which would then cascade to all associated projects. Add a Workload Balancer at the Program level with ability to do Bulk Assignments relative to the cumulative roles identified in the associated projects. How could this work? Expose the Workload Balancer on a Program which would allow ability to assign/override any user on any given project for a selected role. If a Project Manager assigned a user at the Project Level, this would then subsequently override the Program Level assignment; there could even be an indicator carried up to the program level that indicates multiple users or the values as well for a quick display if desired. Current Experience Challenge: Project Managers must either manually assign users task by task, or potentially through bulk edit through sifting throught tasks, or by going to the Workload Balancer for every project. We commonly are running 10-15 projects or more and this requires a very significant amount of time every week to simply assign the same user.
We use the Workfront proofing tool to proof web pages that are created in AEM Sites. Ideally, we would use the URL function within the Workfront proofing tool, to generate the preview of the site and allow the reviewer to review and markup the proof. However, since only designers have AEM Sites access, the reviewer isn't able to view the proof when added as a URL to the proofing tool.Alternatively, the designer is uploading a pdf version of the web page as a document, to the proofing tool. But because it is not a text-based document, the reviewer does not have necessary proofing tools to mark-up text.Is there a way to leverage the URL function of the proofing tool, when reviewing AEM Sites pages prior to the page being published, even though reviewers don't have AEM Sites access? Or can the proofing tool identify text on these pdf versions of web pages (which would enable the text editing proofing options).
Right now i don't see any documentation on how you can create your own custom workflow activity. So people are going in and writing java script code to have that functionality implemented.It will be great to have some kind of documentation to follow on how to create the custom activity the right way and what should be the best practices to create any activity.
Request for Feature Enhancement (RFE) Summary: Multiple domain support for Manage Publication Preview Use-case: My customer APG would like to be able to preview the website in AEM that contains links to multiple domains. The Publication Preview functionality is not following the externalizer configuration to be used properly (screenshot of externalizer domains used below). Current/Experienced Behavior: It is possible to set multiple domains in the externalizer configuration, but only 1 domain is respected in the Publication Preview functionality, resulting in errors in the links when previewing the website (see 'part 2' screenshot below). The impact of multiple domains not being support in the Publication Preview functionality is that it is impossible for APG to properly preview their websites and use this feature properly to identify potential issues. Improved/Expected Behavior: An out of the box solution to support multiple domains for links in the Publication Preview would enable APG to preview their websites properly in AEM. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS feature release 2025.2.0, maintenance release 19823 Customer-name/Organization name: APG Groep N.V. Screenshot (if applicable): Code package (if applicable):
Description - Seed addresses used for internal testing in campaign) are currently included in Adobe analytics reports by default. It can skew engagement metrics.Why is this feature important to you - including seed data inflates KPIs and provides misleading view of actual engagement. Accurate reporting is critical for evaluating true campaign performance, optimizing segmentation and driving meaningful decisions.How would you like the feature to work - Automatically filtering them out from AA reports or giving an option to exclude seed addresses.Current Behaviour - Currently seed addresses are treated like real customers and no out-of-the-box method to filter them out which leads to inaccurate campaign campaign evaluation.
Description - I would like to have the ability to search, sort, and filter the Fusion datastore view. Why is this feature important to you - It's very tedious to find records by visually looking at the datastore. It's also difficult to organize the Fusion datastores without the ability to sort the columns. How would you like the feature to work - I would like the ability to sort by ascending or descending order, filter each column and search the datastore for specific records. Current Behavior - The Fusion datastore is not sortable, filterable, or searchable. The only way to find a record is to manually search each page individually or to use Fusion to search.
Description - As a Fusion Developer, I would like to have the ability to search, sort, and filter the Fusion datastore view.Why is this feature important to you - It's very tedious to find records by visually looking at the datastore. It's also difficult to organize the Fusion datastores without the ability to sort the columns.How would you like the feature to work - I would like the ability to sort by ascending or descending order, filter each column and search the datastore for specific records.Current Behavior - The Fusion datastore is not sortable, filterable, or searchable. The only way to find a record is to manually search each page individually or to use Fusion to search.
Request for Feature Enhancement (RFE) Summary: Cloud Manager Deployment: Enabling Rollback from Previous Build Snapshots Use-case: The customer is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as possible. Improved/Expected Behavior: The production deployment is complete. After the deployment, the customer discovered blocker issues on one of the 24 websites. They wanted to roll back the deployment. They should be able to restart the Stage/Prod deployment using an earlier stable built image. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud (2024.4.16145.20240430T082417Z) Customer-name/Organization name: LG Electronics, Global HQ Korea 24 subsidiaries (UK,DE,PE,TR,JP,FR,SG,CO,SA,SA_EN,CA_FR,CA_EN,KZ,ID,IT,CL,TH,PT,IN,HK,HK_EN,BR ,MX ,PA) Screenshot (if applicable): Code package (if applicable):
Description - When a user's license reduces their sharing permission, this reduced access is not reflected in any of the shared objects today. This leads to issues where someone who is not supposed to make certain changes is still allowed to do so.The system should automatically check on any change being saved to see if their permission has changed. If so, their new sharing rights should override the existing sharing permission. It should also update the sharing rights on the object being saved so that it reflects the new permissions. Why is this feature important to you - To avoid users who had higher privileges, but is no longer privileged, to be able to make changes they should not be allowed to anymore. Currently, it is the responsibility of the object owners to update their sharing, but this is burdensome and error prone since owners may not know they are over-sharing now. How would you like the feature to work - The system should detect a change in permission at save time and prevent changes that are no longer allowed as well as update the sharing rights on the objects being modified. Current Behaviour - No permission checks are done on save, even though their rights have been reduced.
Description - Why is this feature important to you - We've recently discovered that delegated tasks show on Home regardless of the filtering we have set. Most of us have "Not Ready" and "Completed" unchecked -- there's generally no reason for me to see tasks that are not ready for me to work on or tasks that I've already completed. But the "Delegated" filter works separately from the other task filters How would you like the feature to work - I would like the filtering of delegated tasks to work the same as filtering on tasks assigned to me. I don't know why anyone who has "Not Ready" or "Competed" unchecked for their own work would want to see those items for someone else's work that has been delegated to them. Current Behaviour - per current functionality, the following is expected to show on the Home Work List when "Delegated" has been selected: - Delegated tasks that are both ready to start and not ready to start- Delegated tasks that are marked complete will continue to show for 2 weeks after the completion date, after which they will fall off
Simple ideas to enhance administrative review of scenarios: Add a "Description" field that can be populated by the developer to explain the scenario, similar to reporting!Expose this description on the scenarios screen to allow a quick read of the different scenariosAdd extra systemic data such as "created by", "last modified by", "last modified date", "last run date" history etc in the list of scenarios for quick visual
Description - Today, when the Experience Platform Debugger is used by a logged-in user, the component name is pulled right into the debug output, which is great: However, this could be enhanced by a lot by pulling in more details. Some things I would love to see there: The component description Expiration/Persistence settings for eVars List settings for eVars and Props Event settings Existing Classifications This would help to make the debugging experience much easier for less-technical business users. Maybe others have some more ideas? 😊
Description - Expand the functionality for chart colors in reporting. Right now the only way to customize colors is to do so individually. The option to set default colors (ie: that match your companies colors) should be easier than individually changing each item. Why is this feature important to you - Easier functionality for setting up brand colors would help with system maintenance and help make reporting across an instance more cohesive and allow system admins to dictate how colors can be used. How would you like the feature to work - Put it in setup where the other branding options are. Current Behaviour - Manually change each line item in a chart report individually or use text mode.
Description:Enable a native integration between Adobe Experience Platform (AEP) and Databricks to allow seamless data exchange for advanced analytics, machine learning, and large-scale data processing.Why is this feature important to you:Databricks is widely used for data science, modeling, and big data workflows. Many organizations already use both AEP and Databricks but face challenges moving data between the two. A native integration would eliminate friction, reduce reliance on custom pipelines, and unlock more value from both platforms by enabling real-time insights, model scoring, and enrichment of profiles in AEP.How would you like the feature to work:Users should be able to configure a connection to a Databricks workspace directly from the AEP UI. They could export datasets from AEP to Databricks, run transformations or machine learning models, and then write enriched results (e.g., scores, segments, predictions) back to AEP. Ideally, this would support scheduled or triggered jobs and respect identity namespaces and schema alignment.Current Behaviour:Today, connecting AEP to Databricks requires custom ETL workflows, cloud storage intermediaries (like S3 or Azure Data Lake), or APIs. This adds complexity, latency, and cost, and often involves multiple teams. There’s no streamlined, supported connector between the two platforms, limiting agility for data science and activation use cases.
Description:Allow users to upload flat files (e.g., CSV or Excel) directly into Adobe Analytics for temporary, ad hoc correlation with existing data in Analysis Workspace.Why is this feature important to you:Often, analysts receive supplemental data from external sources — like media plans, call center reports, or offline survey results — that need to be compared with web or app behavior. Currently, there’s no easy way to integrate this data quickly for exploratory analysis. This feature would enable faster insights without relying on engineering or data ingestion processes.How would you like the feature to work:Users can drag and drop or upload a flat file directly into Workspace. They can map the file’s columns to existing Adobe dimensions (e.g., campaign ID, date, region), then use those fields like any other dimension or metric in visualizations. The join would be temporary and only available within that session or project, without affecting underlying data.Current Behaviour:Today, adding external data to Adobe Analytics requires a full ingestion process through Customer Journey Analytics, Data Sources, or back-end engineering support. This takes time and isn’t practical for fast, exploratory use cases. There's no native method to correlate external flat-file data directly within Workspace.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK