Hi Team,
Views
Replies
Total Likes
Hi @SwathiKr3,
One way to approach this is by looking at how image profiles are assigned. Since image profiles can be applied at the folder level, the simplest option is to keep the assets with the specific profile in a dedicated folder and then give your user group modify/replicate rights only there. Everywhere else, you can restrict those permissions, which means they’ll only be able to adjust crops where the allowed profile is in use.
Another angle is at the ACL level. The Smart Crop editor is really just modifying renditions/metadata behind the scenes. You can scope permissions down to /content/dam/.../jcr:content/metadata or /jcr:content/renditions/... so that the group has modify rights only for the assets or folders you want, and explicitly deny it for the rest. Deny rules will always override, so you can be very precise here.
If you need something more fine-grained (say, it’s not just folder-based), you might need a small customization. For example, a validator or workflow step that checks the image profile on an asset and blocks/reverts any manual crop edits if it’s not the right profile. That could be done with a Sling filter or workflow launcher on dam:Asset updates.
Hi @SwathiKr3 ,
What you are asking is attribute-based permissions. This is not available OOTB on AEM.
The solution to such a problem is always customization, but the challenge to keep it minimal. For example, I would override the Save button while saving smart crops, it checks the user permissions before actually persisting the edits.
Another solution could be - hiding the Edit smart crop button if the user is not entitled to edit the smartcrops. We have implemented this solution for a similar requirement, it works well. You need some javascript and a servlet to check user's permissions.
I hope it helps, Thanks!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies