Hi @tejaswi_aem, You’ll need to add a clientlib under apps that injects JS in the sites console and page editor context menus, checks if the current user is in xyz-authors, and then hides those actions. 1. Create clientlib - Path:/apps/yourproject/clientlibs/authoring/hide-publicationcq:ClientLibrar...

Hi @Mario248, I don't think so you can use <optgroup> inside an AEM Granite UI dialog the same way you would in plain HTML. The granite/ui/components/coral/foundation/form/select resource type does not support the optgroup element.   Rather do you think these might helpful as an alternateive options...

Hi @PradeepMC1, I think, Adobe does not use your project’s sonar.exclusions configuration by default. As I know, The code quality scan in Cloud Manager is centrally controlled by Adobe and runs its own set of rules with SonarQube. This means that your <sonar.exclusions> or even a custom sonar-pro...

Hi @Balasai_NikhilKa2, Pleae go through these 2 options: Cloud Manager has a built-in Code Quality step powered by SonarQube (Adobe’s managed version). It automatically runs unit test coverage, security scans, style checks, performance checks, and AEM-specific rules. You can configure Quality Gate...

Hi @PradeepDu, Here is what you can do: Verify file paths in GitHub repo In EDS Universal Editor, these JSON files must be located under your repo path:resource/component-filters.json resource/component-definitions.json resource/component-models.json Double-check spelling — in your post one is com...

Hi @GopiTh, Yes, AEM 6.5 and above officially deprecated the Classic UI, and starting with version 6.4, it’s no longer enabled by default - but it’s still possible to enable and use it if needed. Here’s how: Adobe confirms that access to the Classic UI remains available but is disabled by default i...

Hi @FabianaBa, Unfortunately, No! I have experienced this before too: Only Brand Portal Administrators can share collections with specific users or groups. Editors and Viewers can create their own collections, but the sharing options available to them are limited to the “Public” sharing option (li...

In short: You can expose /bin paths, and technically it will work fine. It’s not best practice, because: You lose repository-level access control. It makes governance harder in multi-tenant or enterprise setups. Preferred approach -> use resourceType-based servlets for most cases. If path-bas...

@MatthewDa19  It's not inherently a security risk, but it’s not considered best practice either. With path-based servlets, you lose repository-level access control. With resourceType-based servlets, you can apply auth/authz policies on the resource. That’s why Adobe generally recommends using res...