Hi @Ronnie09 , Can you check the publish log to see the actual request reaching the publish instance? Please also share the shortened URL, the actual full resource path and the configuration to shorten the resource to assist further. Thanks,Fani

Hi @EV909 - I think, the easiest way is to leave the component unlocked, but write a custom CSS (that loads only on the page), which disables the Add/Remove and Edit option on the fields that you want to restrict. 

Hi @Vani1012 , As mentioned by @EstebanBustamante above, Granite Render Conditions is the way to go to handle tab-level permissions on pages.

Hi @Kavin742 , Can you verify if the "Adobe Granite CSRF Filter" configuration is accurate? Additionally, you can update the "Excluded Paths" section with the dispatcher flush path to skip the CSRF check altogether on the flush request. Thanks,Fani

Probably, there's a TTL associated with your content (pages). Worth revisiting the cache strategy, as ideally the page cache should be cleared on publication and TTL-based expiry should be used for static assets like images, fonts, clientlibs.  Thanks,Fani

Hi @T_101 , It might be due to the filter configuration of your project. Try updating the mode for /conf or template path to "replace" in the project's filter.xml and deploy. Should most certainly work. Thanks,Fani

Hi @NathanVieira , You can create a custom component inheriting the core Tabs component, and override the cq:dialog for the desired functionality. This is documented in the "Customizing Dialogs" section in the link https://experienceleague.adobe.com/docs/experience-manager-core-components/using/deve...

Hi @pavan4 , Is that a vanilla instance or the one with some custom code in it. If later, it might have broken as a result of some code or configuration change/installation prior to system restart. Either way, you should find some evidence in the error.log file. Restart the AEM instance, grab the lo...

Hi @brians80208750 - The second icon on your first image (the one with a small wheel to the bottom right) is the one to configure policies for that specific component. This is also present for all the "Allowed components" within your Container component. If you are observing this not present on any ...

Hi @okkk , Are you saying that you see this on adding a component to the page? Can you share the logs as well?