EBoisseauSierra commented on issue #13954:
URL: https://github.com/apache/superset/issues/13954#issuecomment-814121486


   Wow! Thanks for summing that up, this sounds very exciting! Your summary 
covers already a lot (and more than what we could have imagined).
   
   I quite like the idea to be able to send one single report, and use RBAC to 
automagically customise it per recipient. This suppose that each addressee is 
also a user of the Superset instance. This isn't a bad thing from a security 
perspective, yet might make it overcomplicated if people need to setup an 
account just to be able to receive an email. (Fall back to the `Public` role?)
   A possibility _could_ be to enable sending report to non-Superset-users. In 
that case, a nice to have would be for the dashboard owner to whitelist which 
domain name(s) the report can be sent to (e.g. only to `*@mycorp.com` and 
`*@cooldivision.io`). 
   (And, in general, it could be interesting to be able to configure Superset 
so that one can restrict outbound email to certain domain name(s).)
   
   Re caching, a “force refresh graphs” could be added as an option.
   
   As for attachment, we might want to be able to add PDF and/or CSV.
   
   I'm very much looking forward to it! :rocket: 


-- 
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to