[GitHub] shrutimkrishnan commented on issue #504: Access control on the explore page
shrutimkrishnan commented on issue #504: Access control on the explore page URL: https://github.com/apache/incubator-superset/issues/504#issuecomment-321758660 @mistercrunch yup exactly, saw you're taking this feature on in the other entry so thanks a lot! _Sent from my Google Pixel using [FastHub](https://play.google.com/store/apps/details?id=com.fastaccess.github)_ This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] shrutimkrishnan commented on issue #504: Access control on the explore page
shrutimkrishnan commented on issue #504: Access control on the explore page URL: https://github.com/apache/incubator-superset/issues/504#issuecomment-321427988 Tried it out @mistercrunch but not sure if my requirement was the same as described here. I'm looking for user to have restricted access to explore view to only be able to view the chart in greater detail + download the CSV data behind the chart. Right now if I give them can_explore permission they can do everything in the explore view including changing the slice configuration from the left menu which we don't want them to do This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] shrutimkrishnan commented on issue #504: Access control on the explore page
shrutimkrishnan commented on issue #504: Access control on the explore page URL: https://github.com/apache/incubator-superset/issues/504#issuecomment-319835487 Have you had any further feedback on this @x4base - we're trying to understand how to do the same (new to superset!) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
