@Tylopilus got it. I don't think its possible then

@Tylopilus  You can create different groups in the policy as shown in the below screenshot for example. On page authors can choose what they want to apply  

@Tylopilus you don't need to create another component, instead you can have them segregated in Groups in the same policy so that authors apply them accordingly on the pages based on their need.   Hope this helps, Krishna

Project A components are used in Project A templates and Project B components are used in Project B templates.Basically B components are the proxy components to A's components.

Yes, we do this generally for a component but is there any way to create/map policies to embedded component.

  Project A Text Component(/apps/projectA/components/text has resourceSuperType as core/wcm/components/text/v2/text) Above Text Component is included as resource in another component say Component1 So when I author component1 on page -> component1/text is created under page. Project B C...

Hi Team,   Project A - Text Component (has policy that enables all the plugins) - Component 2 (has Text Component as embed resource in it and all plugins are working fine as per policy mapped to text component) Project B - Extending Component 2 from Project A (not getting th...

@mahabubali  Can you try clearing dispatcher cache and verify

sure @Jagadeesh_Prakash will try it once

Hi All,I am trying to setup local aem sdk author instance but getting below error. Tried changing the java versions but could not resolve it.AEM Version: aem-sdk-2022.6.7904.20220629T070041Z-220600Java Version: 11.0.13Apache Maven: 3.8.5 20.03.2023 16:57:45.445 *ERROR* [FelixLogListener] org.apache....