Adobe Experience Manager Sites

I have given access to user for  developer, deployment manager roles  in cloud manager for dev env from admin console.  However this user is seeing the other envrionments when logged in to cloud manger, he can hibernante/dehibernate these envs.  However there is no access to other env when he clicks other env. However He still sees these env links and option to add env button.  Is there any way to restrict env access links and option to hide Add env button on top. 

Hi everyone, I’m looking for some guidance on an architectural decision for a multi-site setup on AEM as a Cloud Service. I need to create additional websites on the same AEM Cloud program. Some of these new sites will share part of the existing platform (authoring model, utilities, or components), while others may require different structures, custom components, or even different frontend approaches. In short, it’s a mix of shared and site‑specific functionality. On AEM on‑prem, my usual approach would have been: - One **common multi‑module project** containing shared utilities, services, and reusable components.- One **separate multi‑module project per site**, each deployable independently (its own pipeline, its own release cycle).- The shared project consumed as a dependency by each site. ### With AEM as a Cloud Service, I’m trying to understand the best practice for this scenario. From what I know, AACS encourages a **single Git repository** and a **single pipeline** per program, b

We facing issue while adding subpages of the page /content/…./…../.../.../future-transformation into the createlanguagecopywizard as the error shown "Resources without a jcr:title property cannot be added to the list." The out of box js which is throwing this error is /libs/cq/gui/components/siteadmin/admin/createlanguagecopywizard/clientlibs/createlanguagecopy.min.js As per the logic, this script tries to render page data using /content/../…/…/future-transformation/{anysubpagename}/jcr:content.json and this request return empty json {}. This is the reason we are getting this error. Kindly help us understand why are we getting this empty json only for these subpages.

Hello, I am using AEM on-prem 6.5.22 and my requirement is similar to  But unfortunately this doesn’t work for me. can someone who faced similar requirements and implemented it help?Regards,Rohit

DetailsThe features in this release focus on Experience Manager Sites, Forms, Assets, and Cloud Foundation innovations and include the following: AEM SITES: Edge Delivery Updates AEM FORMS: Interactive Communications Associate UI AEM ASSETS: AI Search (Multilingual, Semantic) CLOUD FOUNDATION: MCP Server Release Overview Video: https://video.tv.adobe.com/v/3479789/ Seed Q&APlease use this thread to ask questions related to this release.See all the Previous Releases here and the Current Release Notes here.

Hi all, Using Sling Model @Inject Annotation, we could copy JCR node values in to Java variables.Is the opposite also possible, in terms of updating JCR node values from Java variables?If so is there an example? Appreciate all your replies. Thanks,RK.

Hi, Deprecated Library DetectedThe following library is deprecated, but used in your code and so must be removed:Library: ch.qos.logback Deprecated Since: 2022-01-27 Scheduled Removal Date: 2026-02-26Recommended Action:Replace deprecated packages with their recommended newer versions, in order to keep your application secure and performant.  logback library is not used in our codebase. But, I think it is linked and slf4j for logger in our codebase. Please help me in how to scan locally to check if the library is getting used and remove it. Thanks.

We are working on an AEM as a Cloud Service project using Azure DevOps Git as our repo, and our main AEM project includes a couple of Git submodules for shared components and clientlibs. Everything builds fine locally, but when deploying through Adobe Cloud Manager, the pipeline fails to recognize or fetch the submodules. TIA!

hi,We have a requirement to customize the digital forms on AEM 6.5 based on each customer.Currently, the AEM is placed within the intranet and is not accessible by anyone outside.Once AEM publish is placed outside intranet, and can be accessed by the customers, and we have a requirement to capture customer details. I am looking for different ways to authenticate AEM publish, without using LDAP or SSO , as the users are typically external customer and not employees.Kindly suggest different methods. Thank you.

Hi Team, What security measures should be taken care, when one AEM 6.5 publisher and dispatcher is placed outside Firewall. This is required for making it accessible to external customers, but I would like to know what are the security measure that we have to take care for this. Kindly suggest. Thanks.   

In Adobe Experience Manager (AEM), performing a rollout from a blueprint currently requires the initiating user to have at least read access to all live copies associated with that blueprint. If the user lacks access to even one unrelated or newly created live copy, the rollout operation fails—even when the user has full permissions on the blueprint and the intended target live copy.This behavior creates significant operational challenges in large, multi-site or multi-tenant environments where: Editors are intentionally restricted from accessing unrelated live copies New sites are frequently added under the same blueprint Permission models are designed to enforce strict content isolation As a result, editors are blocked from performing legitimate rollouts, while administrators can perform the same action successfully. This forces teams to either over-provision permissions, rely on admin intervention, or introduce service-account-based workarounds, all of which increase operational

We are on AEM in the cloud and have a requirement to send a simple contact form that the user fills out to a backend email address. E.g. no emails being sent to users, no attachments, no data storage, just take the simple form POST request and send an email.AEM has two frameworks out of the box, the older “Foundation Forms” Components and the new “Core Adaptive Forms”.I understand the Foundations Forms are kind of deprecated and Adaptive ones are encouraged, and I understand the new framework has more features, etc.but we already have implemented our custom designs (corporate styleguide) - but for Foundation Form elements only! (buttons etc.)My main question is: can I still use Foundation Forms to send an email (e.g. by building a servlet or in another way), or is it not possible at all in the cloud?If still possible but highly discouraged - what’s the Adobe roadmap for supporting such an approach?Also: is there a way to send the email using an Edge service (e.g. not hitting AEM Publis

We had a query from one of our AEM authors to see if the list component could search and display Tagged pages in multiple folders/paths. Scenario:All our news pages follow the same structure /news/year e.g:/news/2026/news/2025/news/2024etcEach containing 200+ pages in each year folder and tagged accordingly. The University library in this instance, want to show all items tagged with “library” in folders 2026/2025/2024 and possibly more.If they use the List component (using Tags) it doesnt allow the option to search in the child pages. If they use Child option, it allows you to chose a single parent and # of child pages but doesn’t allow you to filter by tag. So, question:Can this component be modified or has someone used this in a way where a AEM Author/Editor can add multiple paths AND search by tag.   

Hi all. One of the steps in a workflow is an approval and that approval link was shared to the end user by email.After he approves/disapproves in the email, how to get the result back into AEM, and specific to the work item in question?Email based approval as a part of Workflow step. Appreciate all your replies. Thanks,RK.

I have recently tried to add a custom action to add a custom action to open the experience fragment in a new tab for a legacy experience fragment component.I used the cq:actionConfigs to add the new custom action like how its done for the core component.The new action button appears in the page editor but not in the template editor.I know we can add actions using Granite.author.edit.ToolbarActions, but before doing that I was wondering if I am doing anything wrong while adding the actionConfigs node? 

I am facing an issue while trying to add actions in my Adobe I/O project using the aio app add actions command. The error I get is:Error: Named export 'loadFile' not found. The requested module 'mem-fs' is a CommonJS module, which may not support all module.exports as named exports.System Details:Node.js Version: v22.13.1npm Version: 10.9.2AIO CLI Version: 10.3.2>aio app add actionsWhen i try to add action, I see below errori Installing template @adobe/generator-add-action-generices, go to https://adobe.ly/templatesi Installing npm package @adobe/generator-add-action-genericchanged 1 package, and audited 1258 packages in 17s176 packages are looking for funding  run `npm fund` for details22 vulnerabilities (5 low, 12 moderate, 5 high)To address issues that do not require attention, run:  npm audit fixTo address all issues possible (including breaking changes), run:  npm audit fix --forceSome issues need review, and may require choosinga di

We are migrating our AEM environment from AMS to AEM as a Cloud Service (AEMaaCS). In our current production environment (AMS), we have 1 Author instance and 4 Publisher instances. One of the custom feature: Whenever a Topic is published (replicated), we need to send Topic content to an external application (from publisher only).Currently, we compare configured sling id with 4 publisher’s sling ID and ensuring sending the content from 1 publisher only. After AEMaaCS migration, how we can achieve the same functionality (identify 1 pod publisher out of multi pod publishers) and then send the published content to external app from 1 pod publisher only.

adaptTo() turns 15 in 2026. From 28–30 September 2026, we’ll meet in Berlin for three days of developer talks and discussions focused on AEM and the underlying open-source stack.Details, tickets, and Call for Papers:https://adapt.toTickets are now available. Loyalty Tickets are available for returning attendees, and Early Bird pricing runs until April 12, 2026.The Call for Papers is open until 5 April 2026 — submit your talk!Please note: This year we’ve adjusted the schedule to allow arrival on Monday morning without missing content.Registration starts Monday at 11:00.Conference begins Monday at 12:00.– adaptTo() Conference Team

Hi Community,I'm setting up Sling Content Distribution (SCD) in AEM as a Cloud Service to replicate content from Author to Publish using a custom agent and Java code.Here’s the agent configuration (com.adobe.granite.distribution.core.impl.AgentConfiguration-myagent.config): name="myagent"enabled=B"true"serviceName="sling/distribution/service/default"serializationType="default"log.level="info"packageExporter.endpoints=["http://localhost:4503/libs/sling/distribution/services/exporters/default"]packageImporter.endpoints=["http://localhost:4503/libs/sling/distribution/services/importers/default"]transportSecretProvider.target="(name=default)"  And here's the code I'm using to trigger the distribution:ResourceResolver resolver = resolverFactory.getServiceResourceResolver(Collections.singletonMap(ResourceResolverFactory.SUBSERVICE, "distributionService"));DistributionRequest request = new SimpleDistributionRequest(DistributionRequestType.ADD, "/content/myproject/en");Distribut

As javax.servlet dependency has been deprecated we are getting tidelift suggestions to upgrade to jakarta.servlet. However, when we update to that we are getting below error -Error: /apps/runner/_work/jabcd/japp-name/core/pom.xml [0:0]: Class org.ab.web.appname.core.servlet.FetchPDF is not assignable to specified service jakarta.servlet.Servlet Suggestions on this error asking again to revert back to javax.servlet. Just checking has anyone encountered this issue before? What solution has been implemented to address this. Pls share your experience. Thanks. -Nilesh

 I'm excited to recognize ​@Tad_Reeves as our AEM Champion of the Month for February! 🤩 👏Over the past two years, Tad has made a meaningful impact within the AEM Champion Program—and even further across the broader AEM ecosystem. From sharing expertise on the mainstage to showing up consistently for the community, his contributions speak for themselves (many of them powered by countless miles on two wheels 🚴🏼‍♂️).Please join me in congratulating Tad on this impressive achievement.

Hello AEM Community,We have an AEM 6.5.21 setup (Author, Publish, Dispatcher) running in our digital platform to serve content. Today we’re using the default AEM user/group administration to provide access for developers and support teams. To improve security and streamline access management, we want to integrate Azure AD SSO and map Azure AD groups to AEM permissions.We’re evaluating SAML 2.0 vs OIDC for best compatibility with AEM 6.5.21, and we’re looking for guidance from anyone who has implemented this in a similar architecture.What we’ve explored so farMany available guides seem outdated. Our current draft approach is SAML: configure the TrustStore (certs) and set up the Adobe Granite SAML 2.0 Authentication Handler.What we’re looking forRecommended approach for AEM 6.5.21: SAML vs OIDC (pros/cons, supportability, common patterns). Granular steps / configuration considerations for Azure AD SAML with AEM: TrustStore / certificate handling IdP metadata / SP configuration details t

Please help me to understand pros/cons between MSM site structure options as below:Option 1:/content/mysite/language-masters/en → /content/mysite/us/en/content/mysite/language-masters/fr → /content/mysite/fr/fr Option 2:/content/mysite/language-masters/en_us → /content/mysite/en_us/content/mysite/language-masters/en_gb → /content/mysite/en_gb