Incubator-superset: How can I only authorize users to dashboards?

[ouyang-lunxi]

Expected results

I want create a role only the given dashboard can be shown to him, but I can only limit his access on datasource. In another word, I want to create 2 or more different dashboards based on the same datasource, and a specified user can only see one of them. But I can't do that based on the existing security model. Is there any suggestions?

[rahulsingh303]

Create user and the assign roles . You can start with Gamma , and create additional roles with custom access to data source.

[mcdavey17]

I don't think data source access is sufficient. ouyang-lunxi says he has two dashboards based on the same data source, and wants to provide (I presume read-only) access to one of those two dashboards. Duplicate of #1799?

[mistercrunch]

For now security restrictions are on a per-datasource only (also, per schema and per database), allowing users to drill-through and slice/dice the data behind the dashboard.

We do understand the use case where the user may be allowed to see a dashboard, but not to explore the underlying datasources and are planning on supporting this at some point.

[LanDeQuHuXi]

+1 read-only public dashboard would be nice

[mojitodaiquiri]

+1 read-only public dashboard would be nice

[teewhyli]

@LanDeQuHuXi @mojitodaiquiri i think that functionality is in the works:
https://github.com/apache/incubator-superset/pull/4725

[isunix]

+1 read-only public dashboard would be nice

[cscainiao]

@isunix Can you elaborate on the implementation steps? Thank you

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[ug911]

Is this feature implemented?

[SonaliSihra]

is this feature is implemented? or anyone is working on it?

[SWoto]

Using the reply from @A. kyenze, I had to change some permissions to enable the user to have the following permissions:

1. Recent Activity
2. Favorites
3. Dashboards Lists

So I ended up having the permissions bellow:
[can list on DashboardModelViewAsync, can dashboard on Superset, can fave dashboards on Superset, can recent activity on Superset, can favstar on Superset, can explore on Superset, can fave dashboards by username on Superset, can csrf token on Superset, can explore json on Superset]

Also had to add (of course) the datasource access rights:
[datasource access on [database_3].(id:3), datasource access on [database_3].table_2]

User Roles
Dashboards
Recent Activity
Favorite

So, because i've a generalViewer, and another role to setup the datasource access, it's really easy to add new daashboards to different users.

[michalmisiewicz]

@mistercrunch Is this functionality in roadmap ?