Need Help wrapping my mind around Filament implementation
Hello!
I recently stumbled across this channel and love the content. Thank you for providing such great videos.
Hoping this group can help me get a better understanding of how Filament might help me with a hobby project I am working on. Fair warning, I am not that great with Laravel, still learning. I am just here to get understanding and learn more.
I want to create an application that let's different departments manage tasks, schedules, notes, etc.
Department heads (admins) would assign tasks through the admin panel. This makes sense to me. They need to be able to see everything related to their department. All tasks, all notes, all schedules, etc.
Each department head can register their own department, then create their own users, and assign tasks, etc. This makes sense to me.
Here is where I am struggling:
1. Users should be able to sign in and only see their tasks and other activities. I would imagine this happens outside of Filament? Does this mean there would be an admin login page but then also a user login page that pulls up their 'work page'?
2. Is Filament just a layer on top of Laravel to give admins access to their 'teams' but the bulk of the app should be handled outside, just in Laravel?
3. All examples I am seeing show that all users 'BelongToMany' teams or clinics in your case. I am assuming MultiTenancy works just as well if users BelongTo one team, or department, in my case?
I apologize for the newb questions and appreciate any feedback.
I recently stumbled across this channel and love the content. Thank you for providing such great videos.
Hoping this group can help me get a better understanding of how Filament might help me with a hobby project I am working on. Fair warning, I am not that great with Laravel, still learning. I am just here to get understanding and learn more.
I want to create an application that let's different departments manage tasks, schedules, notes, etc.
Department heads (admins) would assign tasks through the admin panel. This makes sense to me. They need to be able to see everything related to their department. All tasks, all notes, all schedules, etc.
Each department head can register their own department, then create their own users, and assign tasks, etc. This makes sense to me.
Here is where I am struggling:
1. Users should be able to sign in and only see their tasks and other activities. I would imagine this happens outside of Filament? Does this mean there would be an admin login page but then also a user login page that pulls up their 'work page'?
2. Is Filament just a layer on top of Laravel to give admins access to their 'teams' but the bulk of the app should be handled outside, just in Laravel?
3. All examples I am seeing show that all users 'BelongToMany' teams or clinics in your case. I am assuming MultiTenancy works just as well if users BelongTo one team, or department, in my case?
I apologize for the newb questions and appreciate any feedback.
Solution
1) Users should be able to sign in and only see their tasks and other activities. I would imagine this happens outside of Filament? Does this mean there would be an admin login page but then also a user login page that pulls up their 'work page'?
Yes, that seems to be more fitting than having only one panel (login page) and showing/hiding stuff based on roles.
2) Is Filament just a layer on top of Laravel to give admins access to their 'teams' but the bulk of the app should be handled outside, just in Laravel?
I see it more of a collection of packages (Table Builder, Form Builder, Widgets, etc) that, when put together under the "Panels" package, gives you the ability to create all sorts of admin panels. And no, you can still achieve a lot without having to leave Filament. Unless the "bulk of the app" is like a front facing website that doesn't fit the description of an admin panel (like a blog, for example).
3) All examples I am seeing show that all users 'BelongToMany' teams or clinics in your case. I am assuming MultiTenancy works just as well if users BelongTo one team, or department, in my case?
You can work with simple tenancy, which only needs a BelongsTo relationship on your models. Here's the documentation for it https://filamentphp.com/docs/3.x/panels/tenancy#simple-one-to-many-tenancy
Yes, that seems to be more fitting than having only one panel (login page) and showing/hiding stuff based on roles.
2) Is Filament just a layer on top of Laravel to give admins access to their 'teams' but the bulk of the app should be handled outside, just in Laravel?
I see it more of a collection of packages (Table Builder, Form Builder, Widgets, etc) that, when put together under the "Panels" package, gives you the ability to create all sorts of admin panels. And no, you can still achieve a lot without having to leave Filament. Unless the "bulk of the app" is like a front facing website that doesn't fit the description of an admin panel (like a blog, for example).
3) All examples I am seeing show that all users 'BelongToMany' teams or clinics in your case. I am assuming MultiTenancy works just as well if users BelongTo one team, or department, in my case?
You can work with simple tenancy, which only needs a BelongsTo relationship on your models. Here's the documentation for it https://filamentphp.com/docs/3.x/panels/tenancy#simple-one-to-many-tenancy
