You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/02/03 05:26:06 UTC
[GitHub] [superset] Renganayaki1 opened a new issue #12910: Giving access based on Dashboards instead of Datasources.
Renganayaki1 opened a new issue #12910:
URL: https://github.com/apache/superset/issues/12910
As of now, we can give access based on data sources. If we give permission to one dataset, all the dashboard created using that dataset can be viewed. But what if we need to restrict some of the dashboards here.
We should need the access permission based on Dashboads.
Some of the related Issues, SIP and pull requests i have seen. I have attached all the link below.
1) https://github.com/apache/superset/issues/5483
2) https://github.com/apache/superset/issues/10408
3) https://github.com/apache/superset/pull/12407
So, what is the current status on this? Is the "Access based on Dashboards" option implemeted?
If so, What is the steps to achieve that and from where I can find the option?
Someone please conclude this. Thanks.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 removed a comment on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 removed a comment on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-773069863
> Hi there.
> It is always good to know that others can't wait for that feature ;)
>
> we are working towards the **first** milestone of implementation in which dashboard access can be enforced bases on roles assigned to ( est. in 2-4 weeks)
> but you'll still need to manage the data access in order to allow charts on your dashboard to fetch data
>
> the **second** milestone is to enable data access to all of the charts within a dashboard just by having a dashboard access
> this step is a bit more complex and we still don't have estimates for that but for sure this is something on the short-term roadmap.
>
> hope this concludes everything
>
> Amit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-773071032
Thanks @amitmiran137 for the conclusion. Please let us know once this requirement added.
Rens.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 closed issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 closed issue #12910:
URL: https://github.com/apache/superset/issues/12910
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 removed a comment on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 removed a comment on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-773069863
> Hi there.
> It is always good to know that others can't wait for that feature ;)
>
> we are working towards the **first** milestone of implementation in which dashboard access can be enforced bases on roles assigned to ( est. in 2-4 weeks)
> but you'll still need to manage the data access in order to allow charts on your dashboard to fetch data
>
> the **second** milestone is to enable data access to all of the charts within a dashboard just by having a dashboard access
> this step is a bit more complex and we still don't have estimates for that but for sure this is something on the short-term roadmap.
>
> hope this concludes everything
>
> Amit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 closed issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 closed issue #12910:
URL: https://github.com/apache/superset/issues/12910
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-773069863
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] zuzana-vej closed issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
zuzana-vej closed issue #12910:
URL: https://github.com/apache/superset/issues/12910
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] amitmiran137 commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
amitmiran137 commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-772318634
Hi there.
It is always good to know that others can't wait for that feature ;)
we are working towards the **first** milestone of implementation in which dashboard access can be enforced bases on roles assigned to ( est. in 2-4 weeks)
but you'll still need to manage the data access in order to allow charts on your dashboard to fetch data
the **second** milestone is to enable data access to all of the charts within a dashboard just by having a dashboard access
this step is a bit more complex and we still don't have estimates for that but for sure this is something on the short-term roadmap.
hope this concludes everything
Amit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] Renganayaki1 commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
Renganayaki1 commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-773069863
> Hi there.
> It is always good to know that others can't wait for that feature ;)
>
> we are working towards the **first** milestone of implementation in which dashboard access can be enforced bases on roles assigned to ( est. in 2-4 weeks)
> but you'll still need to manage the data access in order to allow charts on your dashboard to fetch data
>
> the **second** milestone is to enable data access to all of the charts within a dashboard just by having a dashboard access
> this step is a bit more complex and we still don't have estimates for that but for sure this is something on the short-term roadmap.
>
> hope this concludes everything
>
> Amit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] zuzana-vej commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
zuzana-vej commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-822961303
there are linked merged PRs assuming this request can be closed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] pl77 commented on issue #12910: Giving access based on Dashboards instead of Datasources.
Posted by GitBox <gi...@apache.org>.
pl77 commented on issue #12910:
URL: https://github.com/apache/superset/issues/12910#issuecomment-772825105
@amitmiran137 This sounds complex. If a person has access to the dashboard it would seem that they pretty much already have access to the data source, do they not? I guess, from my side, if I wanted to prevent users from accessing various columns or records within a table/database I'd just generate a separate materialized view or other temporary table with the permissible data and give the users full access to that instead. Otherwise it feels like I'll be playing an endless game of whack-a-mole trying to plug various holes to prevent users from tweaking their AJAX calls and grabbing the whole illicit data set.
Anyway, I'll be watching this closely as it might minimize some of my data-post-processing efforts if I can set stronger permissions on data subsets.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org