PBIRS Sep 2026 Bug? Publisher Role Users Cannot View Reports
Hi everyone, I recently upgraded our Power BI Report Server from the May 2026 release to the September 2026 release, and I encountered a critical change regarding user roles and permissions. The Issue: Prior to this update, users who only had the "Publisher" role on a dashboard or folder could successfully view the reports. However, immediately after upgrading to the Sep 2026 version, these users can no longer view their reports and are getting the following error message when trying to access them: "User permissions error: You do not have permission for this operation. Contact your administrator to obtain the necessary permissions." The Workaround: We found that explicitly adding the "Browser" role alongside the "Publisher" role resolves the issue. Since doing this manually for hundreds of dashboards and users was not feasible, I wrote a custom PowerShell script using the native PBIRS REST API to recursively scan the server and automatically grant the "Browser" role to any user who only had the "Publisher" role. My Questions for the Community: - Has anyone else experienced this exact issue after upgrading to the September 2026 release? - Is this an intentional security architecture change by Microsoft in this release, or is it a bug? Thanks in advance for your insights.
Need help setting up Role using USERPRINCIPALNAME() with an extra parameter
Hello everyone! I created a Role where a Partner could only see their own Engagements by using the USERPRINCIPALNAME() measure. It is as follows: If he is a Lead Eng. Partner or and Eng. Partner or and Associate Partner, he should be able to see the Engagement he is a part of. In the following example, Partner B is an Eng Partner for the Engagement 3000431234, so he should see that row. The way I have set up, he can only see the rows his username shows up. However, in this case he would need to be able to see the other Engs. as well because one of the Engagements he is part of is in the Lead Engagement 2001401234. In cases where neither of these two conditions apply, he should not be able to see either the Eng. nor the Lead Eng. Lead Engagement Engagement Lead Eng Partner Email Eng Partner Email Associate Partner Email 2001401234 3000431234 [email protected] [email protected] n/a 2001401234 3000401555 [email protected] [email protected] n/a 2001401234 2001401234 [email protected] [email protected] n/a And that is where I'm having trouble setting up, because in some cases such as this one, the partner isn't in either of those three email fields, but because he is part of the Lead Engagement, he should also be able to see them as well. Any help is appreciated! Thanks!Filter Dimension in Tabular model
Hi, I know this isn't strictly Power BI, but maybe someone in here are able to help. I have a number of Tabular models, where I'd like to restrict which dimension values a user can see. I already have Dynamic RowLevel Security defined to restrict the Fact table, but since it's a "global" Tabular model that contains data for several companies, I'd like to "filter out" the dimension values for the user so he don't have to see data for other companies than his own. The DRLS is created ,so it matches the userID in a table, and this then filters a Legal Company table which then have a relationship to the Fact table. That part works fine and the user only see fact records from his own legal company. I'd then like to so something similar with the dimension data, but since I can't create relationships from the Legel Company table to the dimension tables, then I was thinking about doing it in the Security Role. I was thinking about a rule looking at the Legal Company for the dimension and then "filtering" based on the data from the Legal Company table that only contains the legal company the user are allowed to see. I'm not that experienced in DAX yet, and I can't really figure out how to do it? I have tried various scripts with no luck, so I'd be happy with some idea and guidance. Regards Steen
How to manage data access with DAX
Hi! I need to manage access control over the data in my dashboard. There are multiple countries reporting data. One country in particular (SRO) has sensible data and therefore can only be accessible to members working there. I've created a table where organization members' emails are associated with each of their respective countries. Now, what DAX expression would allow me to specify that only members that login with an email associated to SRO should have access to SRO data? I hope this makes sense, Thanks!RLS functioning is username/ email is not present in the security table
Hi All, Could you please help me with this scenario? If a user is present in the table, I want to implement the RLS based on logged in user using UPN/ Username(). If this user is not a part of the security table, he/she should see all the records, meaning the RLS itself shouldn't be applied/ a way to manage using the DAX in existing table. Could anyone help me tackle this scenario?
