Multy Tenancy
Hi, I’m facing an issue with multi-tenancy ownership on a Resource.
[please check this picture]
Tried
Setting $tenantOwnershipRelationshipName = 'cooperative' works if I add a cooperative_id to saving_accounts, but I’d like to avoid schema changes.
Removing $tenantOwnershipRelationshipName and manually scoping queries with whereHas('member', ...) works, but I'd prefer an idiomatic Filament approach.
Questions
Does Filament v4 support nested ownership relationships like member.cooperative?
If not, is there an official hook/override to implement tenant ownership without adding cooperative_id to child tables?
What’s the recommended best practice from Filament for this case? Is adding a direct cooperative_id on child tables preferred for performance and simpler tenancy scoping?
Thanks!


0 Replies