I don't think AEM has any OOTB permission for this particular use-case.
But, you can always add a custom JS file and include it in the asseteditor.
Categories of that file would be "cq.dam.asseteditor.v2".
- In that file , you can hide ( display:none) , the required buttons based on the URL ( window.location ).
- To make sure they only run for a particular user group, you can call a servlet from the JS file.
- This servlet can send a boolean value in the response based on whether the user logged in belongs to a certain group for which this function should work.
Getting User Groups in Java:
ResourceResolver resourceResolver = getResourceResolver();
session = resourceResolver.adaptTo(Session.class);
UserManager userManager = ((JackrabbitSession) session).getUserManager();
Iterator < Authorizable > groupIterator = userManager.findAuthorizables("jcr:primaryType", "rep:Group");