Funny, before I dared to open this topic, I’ve watched this video as well as other topics.
But unfortunately, this doesn’t solve my problem. Even though your approach gives the ability to assign multiple roles to users, it doesn’t change the fact that Wappler generates its own roles in the sec provider and uses it for the sec enforcer which, unfortunately, only can be applied to whole pages. So it’s kind of a double track. Wapplers user roles, and the ones that are stored in the database itself. That is a shame what I’d like to see is a security enforcer in the app structure itself to restrict access to certain components of the page and not just entire pages. It would already help if not only the identity was accessible on the server side, but also the role the logged in user has.