"Group" feature

[dbrrt]

I was just wondering if the concept of groups could be integrated in this library, or maybe it's already in the roadmap. It could be a nice evolution, but might cost much time to revert/update existing code.

[nicolaslopezj]

I'm not sure in which case this feature would be necessary. Can we discuss here?

[dbrrt]

Yes! I think that groups are essentials when you're building an application designed for several groups of people. Let's assume you've a front-end and a back-end, you'll need to specify a group for front-end users and a group for the back-end, and dispatch specific roles for users that belong the groups. I find it cleaner than "just" setting roles to users. You can also imagine a group per application/module and a resulting hierarchy of roles.

[dbrrt]

So do you think that's something thinkable for next releases or it'll need to many changes in your code and implementations using that package?

[nicolaslopezj]

Mmm why don't create a backend and a frontend role?

[dbrrt]

Actually I would like to implement several groups with different roles for both front-end and the back-end. One solution to do to that with this library would be to code the group in the role : frontend_user, frontend_admin, backend_admin.