Please refer similar question asked in Community with resolution : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/workflow-process-implementation-not-found/td-p/379963    

If CUG is not having anything then yes 10 users will be able to see. If CUG has some group/user other that 10 users then No.

I validated directly on publisher after login from 2 different users. User A from Group A and User B from Group B. I tested on we-retail assets folder and for only User A it was visible in CRXDE.

Only 4 users should have access as CUG will allow jcr:read access to only those users/group which are added at folder level. For other 6 users, even if you give read access it will be non-effective and that folder wont be accessible to them.Refer this screenshot from :  https://experienceleague.adob...

I tried same on we-retail and its working fine in AEM 6.5.13 version. I am able to replicate the above scenario. Its happening when user is not present in Publisher. You can check if rep:cugPolicy node is replicated fine on Publisher under the folder you are replication. This node will have property...

Please check whether the session from which you are creating TagManager object is having proper permission to access those tags. Please refer below snippet from Java Docs :   TagManager interface is generic, but there is a JCR-based reference implementation which can be obtained by the JcrTagManager...

2) Those file will remain in cache directory, until cleared manually. /invalidate section is for file that needs to be automatically invalidated when content is updated. 3) Add rules for assets invalidation. Clientlibs follow versioning, so any update in JS/CSS will create new path for a clientlibs....

There are not any set of properties defined that will come by default on creation. It depends on the setup you have of AEM. Properties like title will always be there but there could be other properties that would come by default based on the integrations you have with AEM. Even properties could var...

You can add one checkbox in dialog and on selection of it you can show/hide the button in Sightly.   Dialog  "items": { "jcr:primaryType": "nt:unstructured", "showbutton": { "jcr:primaryType": "nt:unstructured", "name": "./selected", "text": "Show Button", "value": "true", "sling:resourceType": "gra...

Ideally there should not be performance hit but planning performance testing would give a clear picture. I don't think it can be controlled at dispatcher level as Authorization would be happening in AEM i.e. the last point mentioned in my previous comment screenshot.