Giving end-users access to a Filament panel
The new Filament 3 ability to create multiple panels makes me think that in some cases it might make more sense to let end-users of a website log into Filament to perform certain tasks. But I'm wondering whether there are reasons to avoid this?
Consider, for example, a jobs board. The front end shows job ads, but instead of spending time making a bunch of frontend forms/tables to allow recruiters to post new job ads, and job seekers to apply for ads, you could just make 2 separate panels in Filament (ie: separate from the admin panel) and with a few permissions and filtering so that the recruiter only sees the job ads that belong to them, the recruiter could literally log into Filament to post and manage their ads. And then another panel could be made for job seekers to allow them to apply for jobs and otherwise manage their job applications.
I suppose traditional thinking would be that only website owners/administrators should have access to the admin panel. But now that we can make multiple admin panels within Filament with different permissions only showing a subset of data, is there a reason NOT to do what I've described above?
Consider, for example, a jobs board. The front end shows job ads, but instead of spending time making a bunch of frontend forms/tables to allow recruiters to post new job ads, and job seekers to apply for ads, you could just make 2 separate panels in Filament (ie: separate from the admin panel) and with a few permissions and filtering so that the recruiter only sees the job ads that belong to them, the recruiter could literally log into Filament to post and manage their ads. And then another panel could be made for job seekers to allow them to apply for jobs and otherwise manage their job applications.
I suppose traditional thinking would be that only website owners/administrators should have access to the admin panel. But now that we can make multiple admin panels within Filament with different permissions only showing a subset of data, is there a reason NOT to do what I've described above?
Solution
I think this is pretty much what multiple panels are designed for... If all your permissions are handled properly, I don't see any issues with that.
