Workspace - Securing Content

[RichFlorida]

Hello All, I'm new to worspace security.

Is there a way to hide the Semantic Model or any dataset from users and only allowing them to see and use the Reports and Dashoards.

Pls advise, Thanks!

[pallavi_r · Accepted solution]

Hi @RichFlorida ,

Either i) you can create a separate reports only workspace to pull data from semantic model from another workspace.

 or ii)Provide viewer role to the users who can just see the reports, not any datasets.

Thanks,

Pallavi

[pallavi_r · Accepted solution]

Hi @RichFlorida ,

Either i) you can create a separate reports only workspace to pull data from semantic model from another workspace.

 or ii)Provide viewer role to the users who can just see the reports, not any datasets.

Thanks,

Pallavi

[RichFlorida]

Hi @pallavi_r ,

How do you provide "viewer role" to the users so they can only see reports/Dashboards and not models.?

Thanks!

[SaiTejaTalasila · Accepted solution]

Hi @RichFlorida ,

Providing viewer role to the workspace will be fine.

Please refer this articles-

https://www.brightwork.com/blog/power-bi-share-report

https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-roles-new-workspaces

https://learn.microsoft.com/en-us/power-bi/connect-data/service-datasets-permissions

I hope it will be helpful.

Thanks,

Sai Teja 

[pallavi_r]

Hi @RichFlorida 

You can set viewer role at workspace level.  And model, you can set row level access.

Thanks,

Pallavi

[ajohnso2]

Hi Rich,

You might want to look into splitting your reports away from your models.

For example I have created a workspace were I deploy my models (best practice would be to have 3.)

- Models DEV

- Modelds TEST

- Models PROD

Take advantage of deployment pipelines to keep your 3 environments up to date.

Dont create your user facing report in the same PBIX as your modelling, create a new report and connect it to your deployed model in the service, this new report can be deployed into your user facing workspace (lets call it Reports for simplicity).

Your end users will need read access to the models (not the workspace).

You may see these referred to as Slim Reports.