User has permission to change MetaData field in asset based on group membership | Community
Skip to main content
Level 2
June 14, 2023

User has permission to change MetaData field in asset based on group membership

  • June 14, 2023
  • 2 replies
  • 1526 views

In our Asset meta data we have some drop down fields which contain 'Approved' and 'Not Approved' options.


We would like to limit who can select the 'Approved' for a given field based on group membership.

 

How can this be done? Thank you

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

2 replies

DPrakashRaj
Community Advisor
Community Advisor
June 14, 2023

instead of custom metadata field for this on you should be using the create review task workflow to have this on your assets and you can control who can approve or reject will be controlled by group that has the permission of doing the review.

mbrennanAuthor
Level 2
June 14, 2023

We would like to have a clear view of which assets have been approved in which workflow and by whom.

 

Because many of our assets are at different points in approval, by many different teams it is essential that we can see which approval has been completed in the properties of each asset. 

 

Would having review task give us that kind of overall view on the asset? How could we customize it to?

aanchal-sikka
Community Advisor
Community Advisor
June 15, 2023
Aanchal Sikka
mbrennanAuthor
Level 2
June 15, 2023

Hello Aanchal,

 

I've been able to follow those steps up to

* Open the Advanced section

I'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 users.

aanchal-sikka
Community Advisor
Community Advisor
June 16, 2023

There is no overlay option for the granite:data node


@mbrennan 

The ACLs are to be added to the content, not metadata schema 🙂

Aanchal Sikka