Layout Pages and Security

Working on my application today, hacking my way through it :slight_smile: and I am trying to understand how I should have security setup. I have a admin dashboard were a true admin would log into and create objects such as events, classes out items in events and classes. These people will have an admin role an access the admin dashboard through /wap-admin. I also have users which they will access through there “account” through the frontend but I want to lock down permissions on the user dashboard will be able to be accessed if a user is logged in.

I have 3 layout pages
main - no security
user - logged in user
admin - administrator

Should I just set security per partial page or should I continue to have several layout pages with security set there?

Should the security identifier carry across layout types?

Thanks

Hm, in the beginning I had a similar concern to yours:

The way I’m doing right now is certainly not the “Wappler way”, I’m using Global steps to check the current route and enforce the security there

1 Like

The latter.

1 Like

Have a look at

Has anybody looked at Cerbos?
Very granular Security server that can be self-hosted.

Open source, decoupled access control for your software

There is a Priced product, too.
But

Our open source community edition is free to download. Get in touch to find out about our enterprise offering.
Free forever

Self hosted

Apache License 2.0

All of the core features

An example –