Managing System View Access in Model-Driven Apps

In Model-driven apps, system views play a crucial role in defining how data is presented to users. However, not all users should have access to every view—restricting access to views ensures users see only the information relevant to their roles while maintaining data security and performance.

In this blog, we’ll explore how to manage access to public system views, assign security roles to views.

What Are System Views in Model-Driven Apps?

System views in Microsoft Dataverse define how data is displayed for different tables in model-driven apps. There are several types of views:

1. Public Views

  • Available to all users with table access.
  • Used in grids and subgrids.
  • Can be customized or created by makers and administrators.

2. Quick Find Views

  • Used when users search for records in a model-driven app.
  • Defines the columns and filters used in search results.

3. Advanced Find Views

  • Controls which fields are searchable in Advanced Find.

4. Associated Views

  • Display records related to a parent record.

5. Lookup Views

  • Defines how records appear when selected from a lookup field.

By default, system views are visible to all users who have access to the table. But what if you want to restrict specific views to certain roles?

This is where role-based system views come in.

Why Restrict Access to System Views?

🔹 Security & Data Privacy – Not all users should see every dataset. Restricting views ensures that sensitive business information is available only to the right people.

🔹 Better User Experience – Too many views clutter the UI. Role-based views provide a streamlined experience for users by showing only relevant data.

How to Manage Access to System Views?

Step 1: Enable Role-Based System Views in Dataverse

Use the OrganizationSettingsEditor tool to update the EnableRoleBasedSystemViews setting.




Step 2: Assign Security Roles to System Views

Once role-based system views are enabled, you can assign security roles to each view.

  1. Go to the Power Apps Maker Portal.
  2. Navigate to Dataverse → Tables → Select the Table.
  3. Click on "Views" and choose the view you want to restrict.
  4. Select "View Settings"
  5. Assign Security Roles – Add the roles that should have access to this view.
  6. Save & Publish Changes.






Comments

Post a Comment

Popular posts from this blog

Custom Events in PCF Components

Image
  Introduction In modern low-code development, Power Apps Component Framework (PCF) plays a vital role in enhancing the user interface and delivering rich interactive components. As part of building truly dynamic PCF components, one powerful capability is the event mechanism—especially custom events that allow developers to trigger and listen to component-specific behavior across the app. In this post, we'll explore how PCF components handle events, including how to raise and handle custom events. We’ll also look at practical use cases, implementation steps.   What Are Events in PCF? Events in PCF enable components to communicate with the model-driven app form or other consumers of the control. Microsoft introduced support for custom event handling, allowing PCF control to: Raise events from within the control (e.g., on button click). Notify the hosting form or script when something changes in the control. Enable loosely coupled communication ...
Read more

Dataverse Native Git Integration

Image
Dataverse now offers native Git integration, enhancing the application lifecycle management (ALM) process for developers and makers. This integration enables seamless synchronization of solutions and their components between Dataverse environments and Azure DevOps Git repositories. What is Dataverse Git Integration? Dataverse Git integration is a feature that allows development teams to connect their Dataverse environments directly to Git repositories hosted in Azure DevOps. This connection facilitates the versioning, tracking, and management of solutions and their components within Dataverse, streamlining collaboration among team members. The integration is accessible through the Power Apps interface, making it user-friendly for both citizen developers and professional developers. Benefits of Dataverse Git Integration Centralized Source Control : Git becomes the single source of truth, ensuring consistent and reliable development and deployment processes . Improved Compliance and Secu...
Read more

Set up Power Platform Managed Identities for Dataverse Plugins

Image
Setting Up Power Platform Managed Identities for Dataverse Plugins In this blog, we'll walk through how to configure Power Platform Managed Identities specifically for Dataverse plugins. But first, let's establish a clear understanding of what Power Platform Managed Identities are and why they're useful. What Are Power Platform Managed Identities? Power Platform Managed Identities (currently in preview) enable seamless and secure connections between Dataverse plugins and Azure resources that support Azure Managed Identities. This eliminates the need for manually managing sensitive credentials, like client secrets. Why Use Managed Identities Instead of Client Credentials? Managed Identities simplify authentication and bolster security in several ways: Credential Management : They reduce or eliminate the need for storing and rotating client secrets. Enhanced Security : By minimizing exposure, the attack surface for malicious threats is reduced. Seamless Authentication : They ...
Read more