Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Assets custom metadata schema not visible to some users

Avatar

Level 5

It's AEM cloud runtime.

We created assets custom metadata schema, when applied to the assets, this new tab under assets props can be seen only by users in admin group, how can we make it visible to all the users ?

 

nbg62_0-1661445412874.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @nbg62,

Custom metadata schema are stored under /conf/global/settings/dam/adminui-extension/metadataschema, please make sure your user(s) or user group(s) have at least read permission access to above path. As a reference you can check how it is done in OOTB DAM Users group. You can also add your users into DAM Users - this also should solve the issue.

dam-users-permissions.jpg

View solution in original post

4 Replies

Avatar

Community Advisor

Hi @nbg62 , Can you check in permissions of that user group at /content/dam/.... and allow the user group if required

Screen Shot 2022-08-25 at 1.03.46 PM.png

 

Thanks,

Aditya Chabuku

Avatar

Level 5

hi Aditya,

 

test group can access DAM and all the items in the dam, can delete, upload, etc... but they don't see this additional tab that's coming from custom metadata schema

Avatar

Correct answer by
Community Advisor

Hi @nbg62,

Custom metadata schema are stored under /conf/global/settings/dam/adminui-extension/metadataschema, please make sure your user(s) or user group(s) have at least read permission access to above path. As a reference you can check how it is done in OOTB DAM Users group. You can also add your users into DAM Users - this also should solve the issue.

dam-users-permissions.jpg

Avatar

Level 5

hi Lukasz,

 

it seems that our strict security rules on DAM, in order to achieve that user groups can see only specific folders are causing this problem, this part was the problematic one

nbg62_0-1661517876679.png

 

Our goal was to deny all access to DAM and then allow access and thus visibility only to certain folders

Problem was fixed by changing security to give users read only rights to DAM root, it's not ideal because user can view/read all the folders which we didn't want....

 

nbg62_1-1661518113169.png