xavier-GitHub76 commented on issue #27765: URL: https://github.com/apache/superset/issues/27765#issuecomment-2162733111
I 'm OK with you. Today, list of permissions is very difficult to use when the number of permissions is high. For example, a dropdown list with 170 items is not ergonomic. I think it could be more simple to use if following rules : 1. If an action is enable for everyone, a permission should not exist (like 'can profile on Superset') 2. If an action is not enable for everyone, a permission should exist (like 'can write on Dashbaord') and the buttons linked to theses permissions should be only displayed if permssion is present on role. This would avoid the presence of unnecessary buttons. They will inevitably cause a warning or an error 3. Permissions should be grouped by category to have smaller and easier to understand lists. The categories could be the main elements managed on Superset : - Database - Dataset - Chart - Dashboard - SqlLab - Other Each category could be displayed with tabs :  Your table will be very more pratical to use :  The administrator could thus define a role with simple boxes to check. This would avoid having to interpret an permission based on a technical name. Personally, I don't understand permissions like "can get value on KV" -- 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. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
