GitHub user mistercrunch added a comment to the discussion: Hiding Force refresh in Dashboard
I'm adding a note here as I'm thinking about evolving the security model, and going with a hierarchical action model. I want to make sure that the model we'll come up with will work to support the perm requests across the community. Here the resource would be `Dashboard` and action would be `read.refresh.force`, where composing a role you could specify you give `read.*` minus `!read.refresh.force`. Clearly will require work to attach perms to actions across the frontend/backend, but seems the model I have in mind (and will publish soon) should support this. GitHub link: https://github.com/apache/superset/discussions/32806#discussioncomment-12589418 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
