Restricting Model-Driven App View Access by Security Role

AB-410 By islever Editorial Last updated

Create model-driven apps Implement business and process logic

Short answer

A Restrict the view by assigning it to the manager security role.

Question

A company uses a model-driven app across multiple departments.
A public view intended only for managers currently exposes sensitive columns and filters to all users.
The view must meet the following requirements:
Restrict access to the specific public view to managers.
Display only context-relevant views for other users.
You need to configure view access.
What should you do?
  1. Restrict the view by assigning it to the manager security role. Correct Answer
  2. Configure table-level permissions for managers only.
  3. Remove the view from the app navigation.
  4. Set up the quick find view.

Key Takeaways

Public views are visible to all by default; you must explicitly assign them to specific security roles to restrict visibility.

Learn how to secure sensitive columns in a model-driven app by restricting public view access to specific security roles like managers.

Common mistake: Option B is a common mistake as table-level permissions control record access, not view visibility in the UI selector.

Expert Analysis

In Microsoft Power Apps model-driven applications, view visibility is governed by the Security Role assigned to that specific view. Public views are visible to everyone by default, but administrators can restrict access so that only users with specific security roles can see them in the view selector.

The question requires restricting a sensitive public view to managers while ensuring other users see context-relevant views. Option A correctly addresses this by assigning the view to the manager security role. This ensures that only managers have permission to view the sensitive data within that specific view, while other users simply do not see the view at all, thus maintaining appropriate context for their roles.

Option B is incorrect because table-level permissions control record-level access (read/write), not which views appear in the user interface. Option C removes the view entirely from the app navigation, which does not solve the problem of who can see the view in the view selector if they navigate directly or if it remains accessible via other means; more importantly, it doesn't address the security requirement of restricting access based on role. Option D sets up a quick find view, which is a search feature and does not control access or visibility of specific views to different user groups.

The comments support Option A, explaining that changing the view settings from 'Everyone' to 'Specific security roles' is the correct configuration step.

Official Reference

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/configure-view-security

This link opens the official vendor documentation in a new tab.

Exam Strategy

When configuring views in model-driven apps, always check the 'View Settings' to ensure the correct audience is selected. If a view contains sensitive data, do not rely on table permissions alone; instead, assign the view to a specific security role to control who sees it in the view selector. This method provides granular control over UI elements without altering underlying record permissions.

Frequently Asked Questions

How do I restrict a public view to specific users?

Go to the view settings and change the audience from 'Everyone' to 'Specific security roles', then select the desired roles.

Does table-level permission affect view visibility?

No, table-level permissions control record read/write access. View visibility is controlled separately by assigning the view to security roles.

More AB-410 FAQ →

Community Votes

A
60%
B
40%

60% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. Antea 👍 1 Answered A
    A. Security Roles How to assign a public view to security roles In Microsoft Power Apps: Go to Solutions. Open the solution containing your table. Open the table. Select Views. Select the public view you want to restrict. On the command bar, select View settings. Change the option from Everyone to Specific security roles. Select the security roles that should see the view. Select Save and Publish.
  2. Evincible 👍 1 Answered A
    In model-driven apps, public views can be managed by security role. Assigning the sensitive view specifically to the manager security role ensures that only managers see that view in the view selector, while other users see only views appropriate to their roles
  3. exam_upskill 👍 1 Answered A
    A. Restrict the view by assigning it to the manager security role.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

How to Configure Manager and Position Hierarchy in Power Apps?

S-grade

Configure Business Process Flow Branching and Automation

S-grade

Preventing Table Display Name Changes During Promotion

S-grade

Configuring Visual Insights in Model-Driven Apps

S-grade

← Back to AB-410 Study Guide