Thank you @Hyperbytes for posting the video, as I was just working on this scenario where any user can have multiple permission levels.
Next question on the same topic would be how to implement it with a many-to-many relationship.
As explained in your video, the permissions are forced into the db via a drop-down list. If I want to add a new permission level, I’d need to modify the html code within the page.
Maybe, a clearer separation between model and view would be achieved by having:
- the users listed in a table tb_users
- the permissions listed in a table tb_permissions
- the relationship between the two represented as a many-to-many table between tb_users and tb_permissions
This way, adding a new type of permission would be achieved by updating the db, not working on the html code.
However, it seems to me that such a case cannot be realized by current implementation of Wappler Security Provider.
Any idea? Suggestion? Tks.
Community Page
Last updated:
Last updated: