You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Filament panels are good for managing a lot of records from various models, but it is a bit difficult in use cases where the Panel should only display related records for one model.
Example Users, groups, organizations. IE a form of multi tenancy.
Your current teams set up doesn't really work well for scenarios where a user/ or model is only trying to manage their own data.
There is probably a way to handle this, but it is not really documented or easy to set up. So I'm wondering if you could consider another panel type where everything on the panel should be associated only with the chosen model.
Most everything else should be the same as a normal panel with a few differences.
I'd imagine this would work by
Creating new ModelPanel (panels associated with 1 model)
Define the parent model. (group/ user, etc)
Create new resources... same as normal resources for 1:M or M:M relationships, but all reference the parent model.
Create new Settings Pages -- slightly different from other pages, where it is just a way to divide the form into individual pages instead of tabs. For example, if my Groups table has 30 columns, I can create a few different pages that all handle different groupings of inputs, like permissions, contact info, etc.
Most of these panels would not need a dashboard, though one can still be added if desired.
But panel configuration could include DEFAULT PAGE, ACCESS_BY (criteria for determining who can access)
Like I said, it might be possible to do much of this already, but it is a bit complicated and not really explained in current docs as far as I know. So, making something preconfigured where one only has to define the parent model and access permissions would probably help a lot of people.
sample panel: Some of these tabs may all store data in the parent model table, while others may be related models.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Current Filament panels are good for managing a lot of records from various models, but it is a bit difficult in use cases where the Panel should only display related records for one model.
Example Users, groups, organizations. IE a form of multi tenancy.
Your current teams set up doesn't really work well for scenarios where a user/ or model is only trying to manage their own data.
There is probably a way to handle this, but it is not really documented or easy to set up. So I'm wondering if you could consider another panel type where everything on the panel should be associated only with the chosen model.
Most everything else should be the same as a normal panel with a few differences.
I'd imagine this would work by
Most of these panels would not need a dashboard, though one can still be added if desired.
But panel configuration could include DEFAULT PAGE, ACCESS_BY (criteria for determining who can access)
Like I said, it might be possible to do much of this already, but it is a bit complicated and not really explained in current docs as far as I know. So, making something preconfigured where one only has to define the parent model and access permissions would probably help a lot of people.
sample panel: Some of these tabs may all store data in the parent model table, while others may be related models.
Beta Was this translation helpful? Give feedback.
All reactions