The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
we have a workspace with many semantic models, and we would like to grant contributor access right in workspace to user, allowing them to use the semantic models to build reports.
refer to Roles in workspaces in Power BI - Power BI | Microsoft Learn
Contributor has right to publish/update refresh schedule/modify gateway connection/edit or write semanitc models
But we have some questions:
1. how to disable contributor to edit/update the semantic model?<the semantic model should only be allowed to updated by IT team>
2. how to disbale contributor update the refresh schedule and modify gateway connection? <refresh schedule and gateway should be maintain by IT Team>
Solved! Go to Solution.
Hi @pennyhoho117,
Thank you for reaching out to Microsoft Fabric Community.
There is no direct way to restrict Contributors from editing/updating the semantic model or modifying the refresh schedule and gateway connection while keeping them as Contributors in the same workspace.
If you want the users to use the semantic models to build reports without modifying them, assign "Viewer" role at the workspace level, this prevents them from editing semantic models, refresh schedules, or the gateway. Manually grant "Build" permission on specific semantic models, this allows them to use the dataset in reports but not edit it.
Please note that by removing the Contributor role and assigning only the Viewer role, the user will lose other Contributor-level permissions (for e.g. ability to publish reports to the workspace).
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
Hi @pennyhoho117,
Yes, this is the expected behaviour. We cannot see the semantic model. But we can access the semantic model and build reports from power bi desktop.
Go to power bi desktop --> Get data --> Power BI semantic models, from here we can see and be able to select the dataset to build reports.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
Hi @pennyhoho117,
Thank you for reaching out to Microsoft Fabric Community.
There is no direct way to restrict Contributors from editing/updating the semantic model or modifying the refresh schedule and gateway connection while keeping them as Contributors in the same workspace.
If you want the users to use the semantic models to build reports without modifying them, assign "Viewer" role at the workspace level, this prevents them from editing semantic models, refresh schedules, or the gateway. Manually grant "Build" permission on specific semantic models, this allows them to use the dataset in reports but not edit it.
Please note that by removing the Contributor role and assigning only the Viewer role, the user will lose other Contributor-level permissions (for e.g. ability to publish reports to the workspace).
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
hi
Thanks for your reply,
but we tried to grant Workspace Viewer and Semantic Model :build to users
they cannot see the semantic model in worksapce, it is normal?
they only can see reports in the workspace.
Hi @pennyhoho117,
Yes, this is the expected behaviour. We cannot see the semantic model. But we can access the semantic model and build reports from power bi desktop.
Go to power bi desktop --> Get data --> Power BI semantic models, from here we can see and be able to select the dataset to build reports.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
Hi @pennyhoho117,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @pennyhoho117,
We wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @pennyhoho117,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
User | Count |
---|---|
43 | |
15 | |
13 | |
13 | |
9 |
User | Count |
---|---|
50 | |
43 | |
24 | |
22 | |
18 |