The ideal way to setup permissions
Hi filament community!
New to filament, it's been a pleasure so far. I have a filament deployment with a few panels (admin, ops, service, and community). The service and community are tenanted. I'm looking to implement user management and permissions along with it being configured through the admin panel.
That said, in the past I've always used spatie-permissions to set everything up. However I noticed that filament has a few permission plugins that work off spatie. Before I get to implementing the hasTenants thing - it's logic will be based on permissions and I want to go for the most optimal route:
The way I (naively) see it I have a few options:
1. Using spatie/laravel-permission and implementing it manually (Currently what I have pulled in to my project, haven't implemented much yet)
2. Use Spatie Roles Permission (filament support plugin) which uses spatie/laravel-permission
3. Use Shield by Bezhan Salleh which also uses spatie/laravel-permission and work of that.
I'm inclined to pull in (3) Shield. Would I be correct in saying that I can handle my entire apps permissions using Shield? Sorry if this seems like a dumb question, the descriptions for the plugins were a bit ambiguous for me.
Solution:Jump to solution
Hi @ashattack!
As far as Laravel Shield goes, yes, you can use it to handle your entire application's permissions. I'm currently using it on an application that has a Filament panel for admins and a Vue.js front-end for users, and we're using Filament Shield to manage the roles and permissions for the whole application....
4 Replies
Solution
Hi @ashattack!
As far as Laravel Shield goes, yes, you can use it to handle your entire application's permissions. I'm currently using it on an application that has a Filament panel for admins and a Vue.js front-end for users, and we're using Filament Shield to manage the roles and permissions for the whole application.
@Alex Six all I needed to know - thank you and I love you ❤️
Happy to help! Have fun!
You as well kind sir!