Replies: 2 comments 12 replies
-
Hey there @exorgroup , thanks for the suggestion. At the moment we don't have nothing like that, but nothing stopping you from building a field like that yourself 🙏 It's an interesting use-case tho, so maybe more people would be interested in it. we are currently running a poll where users can suggest and vote for the next features we will build, so maybe you can suggest it there too: #751 If more people are interested in something like this we may give it the proper priority. You can add this, or any suggestion you see fit there. Cheers |
Beta Was this translation helpful? Give feedback.
-
@pxpm |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have implemented this package in the project- thanks for saving some good time
This project may have over 30 tables and each table will require CRUD and print option as well. How everything is set up this means that there will be a very long list of permissions that can get users confused - example country_create, country_edit, country_delete, country_view, country_print and then town_create, town_edit, town_delete, town_view, town_print etc etc etc
Was wondering if there is a possibility of grouping these together so at least the user can see like a heading Country and then the roles attributed to that - ideally having like a collapsible setup so they do not need to scroll through 150 rows or more
Simple way of grouping could be using the underscore to pipe to delineate the groups like setup_country_create, setup_town create and finance_invoice_create. This would imply a structure as following
Setup >
Finance >
Thanks
Beta Was this translation helpful? Give feedback.
All reactions