Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.

AEM Cloud - Cannot remove CUG policies previously configured on publish DAM folders

Avatar

Level 2

In this scenario:


1) adding CUG to folder (on Author instance)

2) publish folder

3) removing CUG from folder (on Author instance)

4) publish folder

 

Does not actually remove this CUG setting on publish instance, after publication.

gangula2018_0-1707236112058.png

 

4 Replies

Avatar

Community Advisor

Hi,

Do you have enough rights to perform this operation? Can you check if there is any error in the log?



Esteban Bustamante

Avatar

Employee Advisor

Hi @gangula2018 , the screenshot looks good. When you add a group/user to the CUG, it will add it there and you will see the group. When you remove the group and publish, it will remove the group and show it how it shows in your screenshot. I tested this and works as expected in cloud. Screenshot attached with CUG group assigned:

 

The CUG settings will remain as it is always irrespective of activate/deactivate

 

Screenshot 2024-02-06 at 7.47.34 PM.png

Avatar

Level 2

The issue is not on the authoring side - it is exactly that when you remove the group and publish, it will remove the group and show it as removed on author - BUT on publish, it will not be removed, and the Publish instance DAM folder will still be accessible by the "removed" CUG and not the others.

There are several ways to test this and confirm the behavior, but it needs to be done on publish instance. There is no issues on author.

Avatar

Administrator

@gangula2018 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.



Kautuk Sahni