Assets Within the Same Folder Have Different Permissions | Community
Skip to main content
S
serdman
April 30, 2020
Solved

Assets Within the Same Folder Have Different Permissions

  • April 30, 2020
  • 3 replies
  • 3960 views

We are having an issue where a user will be able to Edit/Delete and Publish with the following toolbar showing up when an asset is selected:

However, whenever the same user selects a different asset within the same folder they are only able to select Properties and Delete:

All of the permissions for the groups the user belongs to are set at the folder level and the access control panel in CRXDE doesn't show any access control policies are being set for the individual assets themselves. Does anyone know anything that could cause this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by user05162

Can you go to <host>:<port>/useradmin and drill down to the asset level -> check if the user has different permissions for the assets in question. I am pretty sure the permissions at asset level will be different.

3 replies

Deepikaa_Nagesh
Deepikaa_Nagesh
Level 3
May 1, 2020

Hi @serdman ,

 

Maintaining permission at asset level might be too micromanagement and i think it will be difficult to maintain them in future as well.What is the challenge you face in having those set of images in separate folder,because it is always better to have permissions at folder level not at asset level.

May be you can put assets with more privilege in sub-folder.

 

Thanks,

Deepikaa

 

    S
    serdmanAuthor
    May 1, 2020

    The issue is that we don't set any permissions at the asset level and yet these two assets appear to have different permissions despite being in the same folder.

    U
    Adobe Employee
    user05162Adobe EmployeeAccepted solution
    Adobe Employee
    May 1, 2020

    Can you go to <host>:<port>/useradmin and drill down to the asset level -> check if the user has different permissions for the assets in question. I am pretty sure the permissions at asset level will be different.

      Terms & ConditionsAccessibility statement

      Loading footer...