AEM as Cloud Service Pre-filter component list in page parsys or responsive grid based on logged in user

[Som_ChaithanyaGo]

Given that a user is part of project-author group then the component selection window is pre-filtered by the project-component component group, once we click on the Parsys or responsive grid, please find below screenshot, once I log into author instance and open the page, to author and click on parsys to add the component , then need to see project-component group components only in the list, example screenshot I given a sample one showing general group.

[aanchal-sikka]

@Som_ChaithanyaGo 

You would need to adjust the policy of the container, to allow only Project specific components.

The Components on the left-rail is a list of all components allowed on the Page. But, once we click on a container, only the components allowed in the container should be displayed.xs

[HrishikeshKa]

Hi @Som_ChaithanyaGo ,

To pre-filter the component list in a page parsys or responsive grid based on the logged-in user's group membership in Adobe Experience Manager (AEM) as a Cloud Service, you can achieve this through customization using the Access Control Lists (ACLs) and permissions in AEM.

Here's a general approach to implement this:

1. Identify User Groups: Determine the user groups that should have access to the project-component group of components. In your case, this would be the project-author group.

2. Configure Component Group Access: Configure the permissions for the project-component component group to restrict access to only the project-author group. You can do this by setting up ACLs on the component group node in the repository.

3. Access Control Policies (ACP): Create an Access Control Policy (ACP) for the project-component component group that grants read access to the project-author group and denies read access to other groups or users.

4. Apply ACP to Component Group: Apply the ACP to the node representing the project-component component group in the repository.

5. Test the Configuration: Test the configuration by logging in with a user who is a member of the project-author group and accessing the page. When the user clicks on the parsys or responsive grid to add a component, only the components from the project-component group should be visible.

6. Documentation and Communication: Document the access control configuration and communicate the changes to relevant stakeholders, such as authors and administrators.

Keep in mind that implementing access control in AEM requires careful planning and testing to ensure that users have the appropriate level of access while maintaining security and integrity of the content. Additionally, it's essential to regularly review and update access control configurations as user roles and permissions change over time.

[kautuk_sahni]

@Som_ChaithanyaGo Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[Som_ChaithanyaGo · Accepted solution]

@kautuk_sahni   tried multiple options using JavaScript, as we are trying to change the out of the box pre-filter thing, it was not working as expected , so explained to business and they agreed, but in order to display component names first in the list added # to the component name and the components which requires on top of the list came up and business satisfied with it.