web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Couldn't Hide Subareas/Area using Table privilege in model driven App

(2) ShareShare
ReportReport
Posted on by 4

Hey Guys,

 

I'm working on a Model-Driven App and have multiple subareas configured in the sitemap. I’m trying to control the visibility of each subarea based on table-level privileges (like Create, Read, etc.) using security roles.

 

However, even when a user does not have the required privileges, the subarea is still visible in the navigation. When clicked, it shows the error:

 
 

"You do not have permission to access these records. Contact your Microsoft Dynamics 365 administrator for help."

 

My goal is to hide the subarea completely when the user lacks access to the underlying table—but that’s not happening.

Has anyone faced this before or found a solution?

 

Any ideas or workarounds would be greatly appreciated. Thanks in advance!

Categories:
I have the same question (0)
  • Suggested answer
    Anupam.Khasia Profile Picture
    183 Super User 2026 Season 1 on at
     
    This seems unusual behavior, I would suggest updating sitemap from Classic Editor instead of power apps maker portal. 
     
     
    Thanks
    Anupam
  • Suggested answer
    DAnny3211 Profile Picture
    11,417 Super User 2026 Season 1 on at

    Hi,

    Thanks for your question! This is a common challenge when working with Model-Driven Apps in Dynamics 365.

    Unfortunately, table-level privileges alone do not automatically hide subareas in the sitemap. The visibility of subareas is not dynamically controlled by security roles or table access—only access errors are shown when users try to open them.

    Here are a few workarounds you can consider:

    1. Use Custom JavaScript or PCF Controls: You can implement logic to dynamically hide subareas based on user roles or privileges, but this requires custom development.

    2. Create Role-Based Apps: Instead of one app for all users, create separate apps per role with tailored sitemaps. This way, users only see what they’re supposed to access.

    3. Conditional Access via Sitemap Designer: While limited, you can use privilege-based rules in the sitemap designer to restrict visibility based on specific entity permissions. However, this doesn’t always work as expected for all scenarios.

    4. Feedback to Microsoft: Consider submitting this as a feature request via the Power Platform Ideas portal. Many users have requested more dynamic sitemap control based on security roles.

    Hope this helps!
    Please mark this response as helpful if it answered your question.

    Best regards!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 174

#2
ManoVerse Profile Picture

ManoVerse 58 Super User 2026 Season 1

#3
Niki Patel Profile Picture

Niki Patel 42

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans