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 restrict access to the specific public view to managers.
You need to configure view access.
What should you do?
Assigning the nondefault public view to the manager security role restricts its appearance in the model-driven app view selector to users who hold that role. Removing the view from app navigation affects navigation, not necessarily access to the specific view. A Quick Find view controls search presentation and is unrelated to restricting one public view. Table-level privileges secure records and operations across the table; they cannot selectively hide a particular public view while leaving other views available. Role-based system views require the environment feature to be enabled and the view must be eligible for role assignment. The view should be configured for Specific security roles, the manager role selected, and the change saved and published. This restriction controls discovery of the view, but it is not a substitute for data security: sensitive columns and records must still be protected with table, row, or column privileges because access to a view does not grant access to underlying data. Microsoft documents managing public system views through security roles.
Study Guide alignment: Create intelligent applications.
Currently there are no comments in this discussion, be the first to comment!