cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PB2
Level: Powered On

Restrict entity view to a specific security role

Hi,

 

Does anyone know if specific entity views can be restricted to a certain security role? 

 

For example, I have a Product entity with a custom view for new vendor products that only a certain group of people should have access to (the new products are filtered out from every other view). Is there a way to restrict the one custom view?

 

Thanks!

2 REPLIES 2
v-siky-msft
Level 10

Re: Restrict entity view to a specific security role

Hi @PB2 ,

 

I am afraid we cannot restrict Views based on security role, because if the users have Read privilege for the entity, then would be able to see those records.

If they are presented with all the records, then they are in another Security Role, or they are members of a Team, which has been assigned a Security Role with the Read Privilege for that entity.

However, I find that there are some other ways to do it, maybe you can get more ideas from the following blogs:

https://www.powerobjects.com/blog/2014/10/21/assigning-system-views-based-security-roles-dynamics-cr...

http://ms-crm-2011-beta.blogspot.com/2012/09/how-to-hide-some-systemcuctom-views-ms.html

Best regards,

Sik

If this post helps, then please click on “Accept as Solution” to help the other members find it more quickly.

Highlighted

Re: Restrict entity view to a specific security role

If the entity is defined as a user-owned entity, then you could manage this via permissions and sharing. The general approach to take is:

  • Create an owning team that contains all users, and an owning team that contains those users who can view the restricted products
  • Create a security role that grants user-level permission on the entity, and add all users to that role
  • Assign restricted products to the team for restricted users, and assign the other products to the team with all users. You should be able to automate this with a workflow

Note this only works for user-owned entities. You mentioned 'products' in you post; if this refers to the system product entity, this is organization owned, so this approach won't work

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors (Last 30 Days)
Users online (5,194)