Can I apply permissions to assets and metadata fields?

[dmescia2]

I've been told that I can only apply permissions to folders in AEM Assets. Is that truly the case? For our workflows here it would be optimal to point all users to the same images folder but apply permissions to fields in the asset to curate the images. For example, people from certain regions of departments would only see images in that are tagged with their region or department. AEM is the first DAM I've worked with that did not allow for this type of permissioning so its a bit puzzling to me that I'm told this functionality doesn't exist.

[Adilos-Cantuerk]

As far as i know, there is only folder based permissions.
In the DAM i administered before it was as you described.
We had the option to give user groups the right to see and download assets, based of an VDB value.
One one hand, this was very good to have as an option, on the other it was a horror to micro manage.
Usually the regions and departments knew better what asset was meant for them then the people that had to do the micro management of assets. And as long as they could not see a misfiled asset, they did not know of its existence and had no chance to see the error.
In the AEM we currently use different metadata properties to give departments and regions the option to filter out and find easily what they are looking for + some extra folders that contain assets that are strictly for one region only. The structure had to be adapted.
If by chance this tread finds a way to make it possible to have a user group to see only assets with metadata X and another group to see assets with metadata Y - i would be very interested to hear about it.
I am not that unhappy with the way we changed this setting.

[Adilos-Cantuerk]

I just thought about something that feels like an solution but i am very uncertain about it...
and do not know if this is an idea worth of pursuit. 

Have you looked into the search rails "hidden predicate"?
 
Maybe you could... create different search search rails...
depending on user group... and then use the hidden predicate to include/exclude assets (based of the metadata property of your choosing) to make the assets visible/invisible?

[Adilos-Cantuerk]

@kautuk_sahni Do you think that is possible, to create different search rails, that, depending on user group, the user gets restrictions based of the hidden predicate? I don't know if this is even possible - would be great thou.

[kautuk_sahni]

@dmescia2 Did you find the suggestion from @Adilos-Cantuerk helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[digarg]

i think this is possible via customisation, applying permissions to user based on metadata. but we need to write custom logic.

[dmescia2]

We just met with Adobe engineers who mentioned a feature in beta that will allow us to apply permissions to assets based on the metadata. We'll be testing this out over the coming weeks to ensure it meets our use case. I'll report back with the results.

[Adilos-Cantuerk]

I am very interested what comes out of this. Thank you!

[am_DAM_manager]

Has anything come from this discussion with Adobe since you last posted?

[dmescia2]

Nothing yet. We had some competing priorities that to precedence so this got put on teh backburner. I am beginning to map out the user and group permission architecture at the moment so were ready with that when we get the green light from leadership to move forward.

[dmescia2]

I will say that if you are interested in the tag based permissions have a talk with your Adobe rep and see if they can get you into the Beta for it.