Release Wave 2025: Filtered Views in Power Platform Governance
It’s that time of year when we talk about all the new items out in the Release Wave notes! There is a very interesting feature in the Power Platform Governance and Administration section for security data access using Filtered Views.
Introduction to Filtered Views
There is not much information available about this feature and public preview is not available until April 2025. The Filtered Views feature indicates that this will allow administrators to secure record-level access by defining security based on certain values of a field.
Generally, role-based security — meaning where I sit in the business unit hierarchy and my relationship to the owner of the record I am trying to view — defines my access to a record. There are some restrictions with this security model, like when I may have records without an owner or want records to be owned by a system account or similar.
The example given in the release notes describes the need to support reporting and analytical records where there is no record or ownership. These need to be summarized or transformed into data dimensions. I would like more information about how this could be used.
Applications and Scenarios
In several organizations I have worked with, there have been situations with VIP records or confidential records that need additional security. In the current model, it can be difficult to determine how to lock these records down to just the team of users who need access. This can be done with Access Teams or separate business units. However, it can become difficult to fit in with the rest of the security model. This new view-level filtering may help with this request as well.
This is a feature in the Power Platform notes but would apply to any model-driven apps built on Dataverse, including Dynamics 365 Sales and Customer Service.
Business Value
Using Filtered Views, admins can secure record-level access by defining security based on certain values of a field. For example, admins can define access to records where the City field value is equal to Seattle, Bellevue, and Redmond. This security model is critical in securing data access to reporting and analytical records.
Feature Details
Dataverse has a role-based security model where record-level access is determined by record ownership. This security model isn’t sufficient to support reporting and analytical records where there is no record of ownership, as these records are typically summarized or transformed into data dimensions. With this feature, admins can define security roles using filters for certain values in a column.
Key Questions
- How can this feature be integrated into existing security models without causing disruptions?
- What are the specific use cases where filtered views would be most beneficial?
- How does this new feature compare to existing solutions like Access Teams and separate business units?
- What challenges might arise when implementing this feature in large organizations?
- What additional training or resources will administrators need to effectively use filtered views?
Final Thoughts
The introduction of Filtered Views in the Power Platform is a promising advancement for administrators seeking more precise control over data access. By allowing security to be defined based on specific field values, this feature addresses some of the limitations of the current role-based security model. As organizations explore the potential applications of this feature, it will be important to consider how it can be seamlessly integrated into existing security frameworks and what additional support may be needed for successful implementation.
This feature is poised to enhance the security and efficiency of data management in model-driven apps built on Dataverse, including Dynamics 365 Sales and Customer Service. As more information becomes available and the public preview is released, it will be exciting to see how this feature is adopted by the community and evolves.
