Forum Discussion
Report Copy and Semantic Model permissions
Hi. You can create Power Bi Apps to distribute the reports in a workspace to different audiences. That way you could pick what reporting team should see in one audience 1 of the app and what users/stakeholders should see in audience 2. That will let you keep one single workspace with two different sharings. https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-create-distribute-apps
Keep in mind that you can modify the report at the workspace as many times you want, the power bi app will only change if manually the admin click on "Update App". Otherwise, they won't see visual changes, only data refreshes.
If you really need to keep separate workspaces for some complaince policy or security or whatever. Then you could think workspace #1 as your QA environment and workspace #2 as production or the other way around. My point is. Keep all the effort and development in one workspace. Then you need a place to run a code that would move the report and replace it from one workspace to the other. You can do it in azure devops, azure functions, locallly, etc. Then you need a person with coding skills to create an API request or use a SimplePBI python library like this: https://blog.ladataweb.com.ar/post/697833112208539648/simplepbipython-copiar-pbix-entre-áreas-de
I hope that helps,
Super UserHi. You can create Power Bi Apps to distribute the reports in a workspace to different audiences. That way you could pick what reporting team should see in one audience 1 of the app and what users/stakeholders should see in audience 2. That will let you keep one single workspace with two different sharings. https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-create-distribute-apps
Keep in mind that you can modify the report at the workspace as many times you want, the power bi app will only change if manually the admin click on "Update App". Otherwise, they won't see visual changes, only data refreshes.
If you really need to keep separate workspaces for some complaince policy or security or whatever. Then you could think workspace #1 as your QA environment and workspace #2 as production or the other way around. My point is. Keep all the effort and development in one workspace. Then you need a place to run a code that would move the report and replace it from one workspace to the other. You can do it in azure devops, azure functions, locallly, etc. Then you need a person with coding skills to create an API request or use a SimplePBI python library like this: https://blog.ladataweb.com.ar/post/697833112208539648/simplepbipython-copiar-pbix-entre-áreas-de
I hope that helps,