Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This content is archived and is not being updated. For the latest documentation, go to Overview of the Power Platform admin center. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | 
Feb 7, 2025 |
Jun 2025 |
Business value
Using role-based views simplifies the usability of a business line app when multiple users with different needs are introduced. For example, team leads or supervisors working in the case table have different system view needs than a case service rep. Standard system views, like My Cases and My Cases Closed Today, just create clutter for the supervisors. Consequently, makers had to create multiple apps for a cleaner experience.
Feature details
Currently, when users are on a table form, such as an account form, a list of system views is automatically displayed from which a user can choose. Often, this list of views is overwhelming, long, and most of the views aren't relevant to users. Makers and admins don't have the ability to select the views that are applicable to their target users by security role.
With this feature, admins can select the appropriate system views for their respective users by security role. Users with the selected security roles can see the system views that were shared with their specific security role.