Forum Discussion
Workspaces -Not sharing Gateway
Hi ringovski,
Thanks for reaching out to the Microsoft Fabric Community forum.In Microsoft Fabric, go to the workspace where the dataset is located, click on 3 dots next to the dataset, and select Manage permissions to view and modify Build Permissions.
In the Permissions tab, click 3 dots next to a user's name, check for Build Permission, and remove or adjust their role as needed.
If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!
Regards,
Sahasra.
Hi ringovski,
Thank you Akash_Varuna for your response regarding the issue. Mostly, those workarounds work in this scenario. Additionally, I have points to add that may help in resolving the issue.
Users with Build Permissions on a dataset in Workspace A can reuse it in other workspaces. To prevent this, remove their Build Permissions in Workspace A.
As Community member mentioned allow only specific admins to publish datasets in Workspace A and restrict access by removing unnecessary contributors and members. Implement Row-Level Security (RLS) to control data visibility even if the dataset is shared.
Instead of using a single gateway for multiple workspaces, configure a separate gateway for each workspace.This prevents datasets in Workspace A from being accessed in Workspace B.
Glad I could assist! If this answer helped resolve your issue, please mark it as Accept as Solution and give us Kudos to guide others facing the same concern.
Regards,
Sahasra.
Thanks for the reply, where do I find the build permissions? I see user, user with share & admin.
Hi ringovski,
Thanks for reaching out to the Microsoft Fabric Community forum.In Microsoft Fabric, go to the workspace where the dataset is located, click on 3 dots next to the dataset, and select Manage permissions to view and modify Build Permissions.
In the Permissions tab, click 3 dots next to a user's name, check for Build Permission, and remove or adjust their role as needed.
If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!
Regards,
Sahasra.
