-
-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DashboardLayout] Add roles
to navigation
#4490
base: master
Are you sure you want to change the base?
Conversation
I'm hesitant building anything RBAC before we have the CRUD features and have set up a pro version. instead I think we could add a way to disable items through a callback, just like how it's done with treeview or datagrid. that way it and other use cases can be built in userland. use cases which can be then used to validate an RFC. |
We discussed this week that given #4120 is the most upvoted (and fastest growing in upvotes) issue, does it make sense to keep a minimal version of the Once we have CRUD and the pro version, we can integrate the Wdyt? |
My thinking was that there are more ways to do authorization than RBAC. Some users may only need a very simple setup , such as checking against an email address. We could serve more kinds of users with a less opinionated API. Then see which usage parents emerge and provide convenience APIs for the most used ones. I feel like now we're locking every use case into RBAC. |
As @Janpot mentioned, adding a simple callback driving the display of navigation items could solve any RBAC needs as well as many other. (discussed in #4607 ) Then RBAC would just be:
The availability of content can be tackled at the page level by the user as a first approach |
AppProvider
#4120roles: string[]
toNavigationPageItem
groups?: string[]
androles?: string[]
toSession
user.groups
oruser.roles
has a matching role inhasMatchingRole
roles
orgroups
on the session object