Set up security for the Cost accounting analysis Power BI content
This topic explains how you can propagate the access-level security in Cost accounting to row-level security in Microsoft Power BI. This functionality helps guarantee that users see only Power BI data that they are granted access to.
The Cost accounting analysis Microsoft Power BI content uses Power BI row-level security to limit a user's access. Security is based on the access-level organizational hierarchy that is set up in the Cost accounting parameters. For more information about the Cost accounting analysis Power BI content, see Cost accounting analysis Power BI content.
To propagate access-level security to Power BI, the owner of the Power BI content must follow these steps.
The user who publishes the Cost accounting analysis Power BI content automatically becomes the owner. Only an owner can set up security in Power BI. Additionally, until an owner adds other users on PowerBI.com, no one except the owner can see any data in the Cost accounting analysis Power BI content.
Publish the definition file to Power BI.
Sign in to PowerBI.com.
Find the dataset for the Cost accounting analysis Power BI content.
Open the security page.
The Cost object controller role is already created. Add other members who are part of the Cost accounting access-level organizational hierarchy.
Users who are added to the Cost object controller role will see only the data that they are allowed to see, according to the definition in the Cost accounting access-level organizational hierarchy.
Row-level security applies to tiles and reports in Microsoft Dynamics 365 for Finance and Operations that are embedded from Power BI.
If updates are made to access-level security in Cost accounting, and you want Power BI to reflect those updates, you must update the entity store for the Cost accounting analysis Power BI content. After you complete the entity store update from Finance and Operations, you must update the artifacts on PowerBI.com. For more information about how to do an entity store update, see Update entity store. The owner of the Cost accounting analysis Power BI content must also do an entity store update if new users are granted access to the organizational hierarchy. Additionally, the owner must add the new users to the Cost object controller role on PowerBI.com, so that row-level security is applied for them.
We assume that your organization wants to restrict data access. If, for some reason, the security parameters are disabled when you run Cost accounting, the owner must add users to the Cost accountant role in Power BI instead. If you change security from an enabled state to a disabled state, it's a good idea to remove users from the Cost object controller role. And vice versa if you re-enable security. Users can belong to both roles. Joint access is the union of both roles. In the case of the Cost accounting analysis Power BI content, users who have joint access have unrestricted data access. If your goal is to apply restricted access, users must be assigned only to the Cost object controller role. These row-level security updates take effect immediately. Affected users should refresh their browsers.
To learn more about Power BI row-level security, see Manage security on your model in Power BI.