Power Platform Community Forum Thread Details

Hello everyone.

I am developing a model driven app, and I want to hide the area on the sitemap for users with a specific security role.

By Area, I mean the Area shown below according to this website.

Background

1. I have 3 Areas on my Sitemap now. Area_A, Area_B, Area_C

2. There are users with ONLY a Security Role assigned: Read_Only_For_C.

3. In AreaC, there is only subarea (entity) that Read_Only_For_C has read access.

4. Currently, Read_Only_For_C will see all Area_A, Area_B, Area_C

What I want to achieve

I want to make users with Read_Only_For_C be able to ONLY see Area_C (and the subarea in Area_C)

So when they land on the app, they will be in AreaC directly, and they cannot see other Area_Aand Area_B.

What I did

I am following the instruction here Role-Based Sitemap Navigation in Dynamics 365 CE but it just doesn't work for me.

According to this post as well as some other forum, it is suggested that as long as I hide ALL Subareas in an Area, then the Area will be hidden.

Therefore, here is what I did:
1. I created a dummy entity "Navigation_Access". This is for setting the read privileges on subareas.

2. For all other roles EXCEPT Read_Only_For_C, I granted them read privileges for entity Navigation_Access; for Read_Only_For_C it doesn't have any access to Navigation_Access.

3. In Area_A, I go to the sitemap designer, and configured every subareas by setting the privilege: Entity: Navigation_Access, and I checked on Read. Some of these subareas are dashboard, but most of them are entities. But their privileges are al set so.

4. Using Level Up tool to impersonate a user that only has Read_Only_For_C Security Role to log in, did a hard refresh on the page to test the change.

What I observed after the try above

1. I still land on the Area_A, with Area_B, Area_C selectable.

2. Read_Only_For_C can still see most subareas in Area_A and Area_B, with the following content.

3. For some subareas which are entities that Read_Only_For_C has access to, it is showing the content as well.

(i.e. in Area_A, there is a subarea which is entity Student, where Read_Only_For_C has read access, it can see it, although Read_Only_For_C doesn't have read access to Navigation_Access and Navigation_Access is what I configured for Student in the Sitemap)

Could someone please let me know if I miss something here, or if this is feature can be implemented in another way?

Thank you.

Categories:

Building Power Apps