Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Hello everyone,
I have a conceptual question regarding the security and permission model in Power BI Service and would like to validate whether my current architecture follows best practices.
My general goal is to apply a least-privilege security model where every user has only the minimum required permissions, but is still able to view the reports intended for them, see all data they are authorized to see, and export data to Excel, without creating any security gaps.
Current setup
I have the following workspace structure.
Workspace 1: “Semantic Models”
Contains the central dataset.
Access: only me (Admin / Owner)
Workspace 2: “Sales C-Level”
Contains report “Sales C-Level” with 10 pages.
Access granted via Grant Access to 5 users (C-Level)
Workspace 3: “Sales”
Contains report “Sales” with 8 visible pages.
2 pages are hidden.
Access granted via Grant Access to approximately 30 users (Viewer role).
Both reports use the same shared semantic model (dataset) from the first workspace.
Row Level Security (RLS)
In the dataset I defined one RLS role.
Role name: Europe
Filter: D_Country[Region] = "Europe"
Assigned users: 3 users
All other users should have no data restriction and should see all regions.
Additional requirements
All users must be able to export data to Excel (Export data from visuals and Analyze in Excel).
It must not be possible to bypass permissions unintentionally.
The goal is a highly restrictive permission model where each user only has minimal rights, but can fully view their report, is correctly restricted by RLS, and can export the data they are authorized to see.
Observed problem
In practice, I repeatedly experience that some users see no data or unexpected data, filters behave incorrectly, and reports behave differently depending on workspace and user.
Overall, the behavior does not feel reliably reproducible.
My questions
Architecture and best practice
Is this architecture generally considered best practice?
Separate dataset workspace
Multiple report workspaces
Shared dataset across workspaces
Permission model
How should permissions be set correctly in this scenario?
Is it sufficient to grant users access only on the report or workspace level?
Or do users additionally need explicit permissions on the dataset (Manage permissions or Grant access on the dataset)?
RLS design
Is it sufficient to define only one RLS role called Europe?
Or should I also create a second role like All without any filter?
Do users without any RLS role automatically see all data or must they be explicitly assigned?
Link sharing and forwarding
Is it possible that User A forwards a report link to User B and thereby bypasses permissions?
Or does Power BI always strictly validate permissions on report and dataset level when opening a link?
Export to Excel
Which permissions are required so that all users can export data to Excel?
Are there any special considerations in combination with shared datasets, Viewer permissions and RLS?
Known pitfalls
Are there any known best practices or common pitfalls with shared datasets, multiple workspaces, and the combination of Viewer role, RLS, export and link sharing?
Thank you very much for your help and guidance on best practices.
Hi @showy123
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank you
Hi @showy123 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Hi @showy123 ,
Thanks for reaching out to the Microsoft Fabric Community forum.
Organizing workspaces effectively is a critical part of workspace planning. Different business units and departments may use workspaces in different ways based on their collaboration needs. When creating a new workspace, it’s recommended to take these factors into account to ensure the workspace is set up appropriately.
You can check them out in this article here:
Implementation Planning: Workspace-Level Workspaces - Power BI | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Thank you
Hii @showy123
In Power BI Service, the best-practice security model is to separate content, data, and security: keep shared datasets in a dedicated “data” workspace, apply RLS only on the dataset, and give users access to reports via Apps or report workspaces (Viewer role) rather than direct dataset permissions. Avoid granting Build / Read on datasets unless needed, because export and Analyze in Excel are controlled at the dataset permission + tenant setting level, not by report access. Use Azure AD groups for all access, control exports centrally, and remember that RLS always applies, even when users open reports via links, apps, or Analyze in Excel unless they are dataset Owners/Admins.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 20 | |
| 11 | |
| 10 | |
| 9 | |
| 8 |
| User | Count |
|---|---|
| 51 | |
| 37 | |
| 29 | |
| 27 | |
| 18 |