I am in the planning stage of an app that will require fine control of permissions. What I mean is, it won't just be whether a user is logged in, but whether a user is in a particular group as to what pages are viewable and even what modules are viewable or even the behaviour of those modules,
e.g. an email module may let you send single or bulk email if you're SUPER_ADMIN, send single emails and request bulk email to be sent if you're ADMIN or have to request any email being sent if you're STAFF or only view emails if you're STUDENT and base case see nothing if you're USER or GUEST.
I was thinking of implementing a route table in the database to store the routes so that I can manage what groups/users can do what with each page, and have a default DENIED permission on new routes that become available. The problem with this approach is making sure I get all routes and accommodating variables within those routes.
Does anyone have an idea on how to implement what I am talking about? I would love to have it all just automatically happen once the functions are set in place without having to maintain the table everytime the app gets work done.
Sentry, as zenry noted, can handle all that. Give it a hwirl.
Sentry is what you are looking for if you need something at the global level.
If you need resource-level ACLs, Redoubt is the way to go: https://github.com/greggilbert/redoubt
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community