Apache Superset Roles Authz Logic

[hollow crypt]

Hey @azure hull ,

Absolutely give us a little bit of time to generate an example schema that you can head start with 👍🏻

[azure hull]

Thanks a lot @hollow crypt

[azure hull]

you might already be aware, they have a terminology models on which these permissions apply; ex: models are: dashboard, embedded_dashboard, filter_set, user_attributes, slice (A slice is essentially a report or a view on data), user;

it appears like models are synonymous to entities .. in permify; @hollow crypt

[azure hull]

I made an attempt this way, https://play.permify.co/?s=PVMIkkatZ20_Sve0IUYcr

but i feel like should i model all permissions as attributes and assign attributes to respective roles; to represent a user with respective role??

please guide;

[hollow crypt]

The model you send is a one way of doing it.

Honestly couldn't quite understand the second question but as long as I understand, it's not a best practice to model all the permissions with attributes.

I'm sending you another model that can help you with the head, which is more granular in terms of permissions, a few secs please 🙂

[azure hull]

sure, you got me right; i was looking for representing permissions with attirbutes; I take your word; will wait for your model. thanks.

[hollow crypt]

Hey @azure hull

You can design ever permissions object as an entity at the Apache Supersets.

For instance there is log reads and writes, so log can be a entity, and would had read & write as a permissions.

You can even create permissions based on logs not just dashboards.

Here's a quick example; https://play.permify.co/?s=85AJpeF6_g4ZlBY0sTzS4

[hollow crypt]

Does it make sense @azure hull?