Hi Anil, Thank you for your responsel Your wording here is not clear "Is the ask to limit the user to publish the assets but not publish to brand portal Only?" I would like to limit the users who can publish assets to brand portal. I understand the concept of user groups and requirements and would l...

If I would like only one user, or one group to be able to publish to brand portal. What permissions can I set for that?

I tried following this schema based on the metadata field and it was unable to limit based on group permissions. http://www.xicojunior.com/blog/2015/12/19/enabling/disabling-tabs-on-aem-6.1-assets-metadata-schemas-using-groups/

How can I add them to the content instead of the metadata schema?We would like these permissions to translate over all assets.

Additionally I went back through and overlayed the created grantie:rendercondition nodes to app. However the options are still visible in the drop down

I am able to create nodes granite:rendercondition"/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/ugc/granite:rendercondition""/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/createlivecopy/granite:rendercondition""/libs/dam/gui/content/assets/jcr:cont...

This is working for me! I was able to change most of the menu options. There are a few outliers-import ugc - only has data nodecreate live copy - only has data nodemetadata - has no child nodes"/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/" 

There is no overlay option for the granite:data node

Hello Aanchal, I've been able to follow those steps up to* Open the Advanced sectionI'm not sure what the advanced section should contain as this is a custom field in a metadata schema  I've restricted privileges based on group to the granite:data node but the restrictions are not showing up for use...

I tried reverting the node but that did not work.