> > If we want to model with the permissions then we should be able to add the > permissions dynamically, but this is not possible with current carbon - > 4.x. And as I have mentioned above, this cannot be included in the global > level as well, because having a settings or delete privileges for dashboard > - X, doesn't mean you have the same privileges for dashboard - Y. And hence > we thought of going with roles approach for this one as well. I agree, the > role names for settings and delete is bit odd, we need to come up with > proper names for those. :) >
I think it is possible to dynamically create any permissions via the API even in C4 2) Does "settings" make sense, because if you are an editor, anyway you'll >> have full access to the JSON, don't you? > > In settings you have the full privileges, ie, you can even remove the user > who initially created the dashboard, IMHO it provides the full control of > the dashboard. Designer doesn't have such privileges, he/she can only > add/remove gadgets, pages etc which is related to designing the dashboard. > Therefore we need to have a different role to control the access of the > settings page. We may call this "Owners"? -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
