Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

User action permission possible?

sumitc22
Level 4
Level 4

Hi,

I have a requirement of user permission like below from client :

Eg, Role 1 can upload/download an asset but can't edit. They don't want specific folder permission. Is it achievable in AEM ?

                         

 

Download

Upload

Edit

Approve

Admin

Role 1

l

l

   

Role 2

l

l

l

l

 
1 Accepted Solution
Jörg_Hoh
Correct answer by
Employee
Employee

Hi,

From a repository perspective upload and edit are essentially write operations, so they cannot be reflected directly into repository ACLs. If you need to differentiate between these 2, you should consider to use workflows for uploads and deny write access to the DAM for the role1. Then you have to implement the upload via a workflow and you cannot use the nice drag-and-drop features to upload assets to DAM from your desktop. You have to code then your own upload dialog and upload the files to a temp folder, where the workflow is started. That's not a real nice solution, and requires some major work to make it work well.

I don't think, that this requirement is useful, when users have the ability to directly upload images via the authoring UI.

kind regards,
Jörg

View solution in original post

1 Reply
Jörg_Hoh
Correct answer by
Employee
Employee

Hi,

From a repository perspective upload and edit are essentially write operations, so they cannot be reflected directly into repository ACLs. If you need to differentiate between these 2, you should consider to use workflows for uploads and deny write access to the DAM for the role1. Then you have to implement the upload via a workflow and you cannot use the nice drag-and-drop features to upload assets to DAM from your desktop. You have to code then your own upload dialog and upload the files to a temp folder, where the workflow is started. That's not a real nice solution, and requires some major work to make it work well.

I don't think, that this requirement is useful, when users have the ability to directly upload images via the authoring UI.

kind regards,
Jörg

View solution in original post