Creating a Dashboard needs edit-permission, why?

[Nameless_LW]

I'm having hard time to understand, why creating a dashboard requires edit-permissions to the target report.

In the official documentation (https://learn.microsoft.com/en-us/power-bi/create-reports/service-dashboards#who-can-create-a-dashbo... it says:

The ability to create a dashboard is considered a creator feature and requires edit permissions on the report.

To me, that sentence does not make any sense, when it comes to the purpose of a dashboard. The documentation (https://learn.microsoft.com/en-us/power-bi/create-reports/service-dashboards#dashboard-basics) describes dashboards as:

A dashboard is an introduction to the underlying reports and datasets. Selecting a visualization takes you to the report and dataset that it's based on.

The only thing the user want's is to collect some visuals from reports to a single dashboard. The dashboard doesn't need to be created to the same workspace with the report, it could be created to users own "My Workspace", where the user has edit-permissions in order to edit the contents of the dashboard.

I can understand the use case where the report designer creates a shared dashboard for a bunch of users. This dashboard should be edited only by the people who know what they are doing. But when it comes to a "personal dashboard" use case (which I thought the dashboard-feature was originally created for), the permission requirement should not be necessary.

Is this just a technical limitation?

[ibarrau]

Hi. I'm sorry but I don't think you will get an answer here about why a feature was developed like that in a forum. We can "guess" why it make sense for us, but it won't be the real reason.

I think it make sense to keep it this way. The idea is always to make reductions and let data become information in a place that works the same for everybody. Otherwise each user will make mistakes and have different numbers. In addition, keeping in the same workspace help on a security stand point to understand what contentn and users are in there.

Again, that's a thought. I hope you can make sense of answers we might write.

[Nameless_LW]

---

@ibarrau wrote:

Hi. I'm sorry but I don't think you will get an answer here about why a feature was developed like that in a forum. We can "guess" why it make sense for us, but it won't be the real reason.

I think it make sense to keep it this way. The idea is always to make reductions and let data become information in a place that works the same for everybody. Otherwise each user will make mistakes and have different numbers. In addition, keeping in the same workspace help on a security stand point to understand what contentn and users are in there.

Again, that's a thought. I hope you can make sense of answers we might write.

---

I couldn't agree more, especially with the bolded section of your answer.

That's the thing, why make the very useful feature sort of "crippled" ? I as a report developer am not keen on giving the users additional permissions just because I want them to be able to collect the things they want to a single, personal dashboard. With the extra permissions, they can misclick and delete the whole report or edit the report to an unusable state.

Maybe it's just me and everybody is nodding like "well yes, this was exactly what we wanted, what is this guy whining about"