Filament: User / Team Admin / Super Admin - Boilerplate
Вставка
- Опубліковано 7 лип 2024
- Let me show you a simple demo of a task management system with users, teams and roles.
GitHub repo: github.com/LaravelDaily/Filam...
More Filament examples on our website: filamentexamples.com
Great explanation!! keep doing tutorials like this! Core concepts, how to resolve functionality... U rock!
Thank you! I’m still working on the same project (open Source), which involves using multiple panels for various teams, projects, and tasks using Filament PHP. I'll be posting updates on Twitter soon.🙂🙂
Hello. Please make an example of a role management page with filament and laravel-permission.
Thank you for providing this valuable solution. It would be even more effective if user registration were disabled, allowing the superadmin to create teams and assign administrators to those teams. Subsequently, team administrators could add users under their respective teams.
Every app is different. What you mentioned isn't hard to do. A basic user resource
Yes it's another way of registering new teams/users, in general there are multiple OPPOSITE approaches of who can register which layer, unfortunately impossible to do them all in one app, so I've chosen a different option.
Amen sister!
What plugin you use for fill the form?
Fake filler
Would it be feasible (and a good idea) to move the team global scope to a trait that can be reused for other models that might require the same functionality?
Yes, one of the options, depending on how "globally" you need that condition :)
Hi
I am facing performance issue while loading 100 records on list page.
Can you please give me improvement suggestions?
Thank you
Can you give more details, how you measure the performance?
Very nice Povilas. I actually work on a project in filament to manage a Sport Team, and this video is a great starting point for the roles.
But in my case, in the admin panel I have to manage some features (athletes memebership, race subscription from athletes. payments), so I have lot of different admin roles (accountant, registration officer, secretary and president). So I have the situation where a specific user could be secretary and accountant, or other combination (of course president should manage everything).
In my case I think that I need a many-to-many table for role-user, but for me it's not clear if I have to use even a permissions table.
Is Shield the correct package for me or it is excessive?
Shield is only the ui for spatie laravel permissions package which I would totally use and would recommend
Personally, I've been always skeptical about such multi-role approach. Is a personal REALLY accountant and a secretary, adding more complexity? Or is it the case of creating a new role like Senior accountant, assigning the permissions?
@@FilamentDaily i'm skeptical too, it's the first time for me with this approach, but now I have this situation:
-admin role: can manage everything, like a maintenance user;
-president: can manage everything like the admin, and assign roles to other users;
-secretary: can manage new users memberships;
-accountant: can manage payments and deposits
-registration officer: can manage races and users subscription to races.
-advisor: can view everything, but cannot create, delete or modify nothing.
-simple user: can access their profile page.
At this moment we have only one person for each "role", and they are different persons, but what if in the future an advisor needs to manage races and payments?
If I not use multi-roles how to manage this possibile situation?
I overthinking?
Personally, I don't like to think about "in the future", I solve the problems when they come :)
Worst case, the company would share the login credentials between themselves :)