1. Home
  2. General
  3. RE: Remove add button for new Web Content in Asset Libraries

RE: Remove add button for new Web Content in Asset Libraries

Jamie Sammons, modified 2 Years ago.
Remove add button for new Web Content in Asset Libraries
New Member Posts: 2 Join Date: 6/19/23 Recent Posts

Is there a role that takes away the permission to a user to add a new web content in Asset Libraries?

I need to create a role that gives the user only the ability to publish to live. I managed to remove all other permission but I can't on this one in particular.

 

 

thumbnail
Russell Bohl, modified 2 Years ago.
RE: Remove add button for new Web Content in Asset Libraries
Expert Posts: 308 Join Date: 2/13/13 Recent Posts

I don't know much about asset libraries, but when I give my user the Asset Library Administrator Role, they don't seem to have the ability to add assets in the Asset Library. However, the add button appears if I give them permissions to add Web Content resources. So I think you'll have to manage it through the web content resource permissions, in the Site and Asset Library Administration > Content & Data > Web Content section of a role's define permissions UI.

Jamie Sammons, modified 2 Years ago.
RE: RE: Remove add button for new Web Content in Asset Libraries
New Member Posts: 2 Join Date: 6/19/23 Recent Posts

Thank you Russel, I've tried so many combination with the web content resource permission but yet not of them did the trick. At this point I am not even sure it is possibile, it seems that publishing and adding are somehow related. 

thumbnail
Russell Bohl, modified 2 Years ago.
RE: RE: Remove add button for new Web Content in Asset Libraries
Expert Posts: 308 Join Date: 2/13/13 Recent Posts

Are you sure the user is not the Asset Library Owner? If you go to the asset library, Memberships screen, you can filter by role--choose Asset Library Owner and see if the user you're trying to limit has that role. If they do, I don't think you can take away the add permission.

If you think the publication permission is responsible, try disabling publications, perhaps, to test it out?