Workspace Viewer with Build can't copy a report in their personal workspace

[mlovejoy]

Hello Community,

I don't understand if I'm doing something wrong or is it just a huge common sense failure from Microsoft. 

Why can a Viewer in a workspace with Build permission create a new report from scratch with a dataset but not copy the existing report in his workspace?

To allow him to copy it we would need a contributor level which will allow him to potentially break the "main report" and completely disable his Row Level Security.

Is this right? Is there a Turnarround? Or is this just completely stupid?

It's like you have 3 God Level of permission and a slave poor usless Viewer Level of permission. This needs a fix.

Regards,

Mark

[collinq]

Hi @mlovejoy ,

I am not sure that this is a failure in the system.  BY definition a "Viewer" only has ability to view and item.  If you are giving a user Viewer permissions then they do not have Build permissions.

If you are also giving a user Build permissions separately then you are telling the system that you do not want them to be just a Viewer.  You are elevating that person's rights beyond just a Viewer.

Therefore, you are right, they need to have contributor access if you want them to copy or modify the data.

The setup is working fine and I respectfully submit that it is not stupid -  it just appears that you have a unique use case that is not very common. If you want them to make their own reports from a dataset and not modify the existing dataset and/or reports in an existing workspace then you can either create a dataflow, datamart or even put the dataset you have created into it's own separate workspace where you give the rights to build.