Permission Required error

[funklordofusa]

Hi,

I have created a dataset that is used for reports I have shared in an app.  Some users, not all, are getting the following error when trying to access the report.

Permission required: you cannot see the content of this report because you do not have permissions to the underlying dataset...

The problem is I haven't defined any permissions to exclude any viewers.  I do not have any viewer roles created, no row level security, no anything that I think of that would cause a user to be snubbed.  Users all have pro licenses.  I deleted an existing workspace, created a new one, published the reports to the new workspace, and updated a brand new app but the users are still prohibited.  I do have one user that has access and the app functions as intended.

Does anyone know what may be happening?  Or what I may be able to do to help the users gain access?

Thanks for your help,

[venal · Accepted solution]

@funklordofusa 

I tried to re-pro the issue from my end.

Analyzing that you need to add the user under the dataset.

Ex:- Report Name:- Sample.PBIX

select the workspace >> go to the data sets tab >> select the data set >> clcik 3 dots at the end of the data set >> Manage Permissions >> Add your user to the dataset and assign them the role as "Read".

Hope it will resolve your issue after assigning the role.

If you have any queries, please let us know.

If this post helps, then please consider Accept it as the solution to help the other members find it more
If this post was helpful may I ask you to mark it as solution and click on thumb symbol?

[funklordofusa]

Adding the specific users did resolve the permission error.  Thanks.

I did already have a user/group with access called "Entire organization" but I guess that didn't function.  Another interesting anecdote is that the individual user that always had access doesn't explicitly have their name included in the Users With Access list.

I'm still a bit confused but at least the consumers can see their reports for now.

[vnl3]

We have this same issue and the aforementioned recommendation did not work. Please advise.