Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi,
We are implementing Power BI in our company and we have an important question about how to manage reports for external clients securely. We want to give each client access to only their report, without being able to see reports from other clients. We would like to publish multiple reports in a single workspace (one per client), and then share only the relevant report through a Power BI App to each client.
Is it secure to keep multiple client reports in a single workspace and use Apps to restrict access?
If a client only has access to the App (not to the workspace), can they somehow see or know there are other reports?
What if a client is accidentally given Viewer access to the workspace — will they see all the reports in it?
Is it best practice to create a separate workspace per client to ensure full isolation?
Is there any way to restrict access more granularly without splitting into multiple workspaces?
Thank you for advance
Solved! Go to Solution.
Hi @Martapv,
Thanks for reaching out to the Microsoft Fabric Forum Community.
1. Using a Single Workspace with Apps. Secure if configured correctly. Apps only show selected content to users. Regular permission testing is essential.
2. Client Access to App Only, Clients cannot see other reports in the workspace if they only have access to the App. App visibility is limited to shared content only.
3. If Client Gets Viewer Access to Workspace. Yes, they will see all content in that workspace. Avoid giving clients workspace access unless necessary.
4. Separate Workspace per Client (Best Practice). Ensures complete isolation of data and reports. Simplifies permission management and minimizes risk.
5. More Granular Control Without Separate Workspaces. Row-Level Security (RLS) limits data visibility within shared reports. Apps can restrict report access, but need careful setup.
6. Azure AD Security Groups. Use groups for scalable access management. Assign roles and permissions based on group membership. Enhances control and reduces admin overhead.
If this helped, please mark the response as the accepted solution and give it a thumbs-up so others can benefit too.
Best regards,
Prasanna Kumar
Hi @Martapv,
We wanted to kindly check in to see if everything is working as expected after trying the suggested solution. If there’s anything else we can assist with, please don’t hesitate to ask.
If the issue is resolved, we’d appreciate it if you could mark the helpful reply as Accepted Solution it helps others who might face a similar issue.
Warm regards,
Prasanna Kumar
Hi @Martapv,
Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.
If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful this will benefit others in the community as well.
Best regards,
Prasanna Kumar
Additional note:
It is important to mention that each report will be accessed by a large volume of users, so our intention is to manage access using Azure AD security groups (not individual users). These groups are already defined by client or role.
We are looking for the most scalable and secure way to manage access without duplicating workspaces unnecessarily.
Hi @Martapv,
Thanks for reaching out to the Microsoft Fabric Forum Community.
1. Using a Single Workspace with Apps. Secure if configured correctly. Apps only show selected content to users. Regular permission testing is essential.
2. Client Access to App Only, Clients cannot see other reports in the workspace if they only have access to the App. App visibility is limited to shared content only.
3. If Client Gets Viewer Access to Workspace. Yes, they will see all content in that workspace. Avoid giving clients workspace access unless necessary.
4. Separate Workspace per Client (Best Practice). Ensures complete isolation of data and reports. Simplifies permission management and minimizes risk.
5. More Granular Control Without Separate Workspaces. Row-Level Security (RLS) limits data visibility within shared reports. Apps can restrict report access, but need careful setup.
6. Azure AD Security Groups. Use groups for scalable access management. Assign roles and permissions based on group membership. Enhances control and reduces admin overhead.
If this helped, please mark the response as the accepted solution and give it a thumbs-up so others can benefit too.
Best regards,
Prasanna Kumar