- What does jeffersongoncalves/filament-teams do?
- It is a Filament plugin that adds multi-tenancy with teams, memberships, and team invitations to your Laravel admin panels. It provides a ready-made interface for creating teams, inviting members, assigning roles, and managing team resources. It is designed to be composed into an existing Filament panel provider rather than used standalone.
- How do I install filament-teams in a Laravel Filament application?
- Install it with Composer using composer require jeffersongoncalves/filament-teams, then publish and run the package migrations and publish its config. Next, register the plugin in your Filament panel provider and wire your User model into the team and tenancy contract the package expects. Follow the standard three-step Filament plugin path rather than running the published migrations blindly against a populated users table.
- Which Laravel and Filament versions does filament-teams support?
- The surrounding evaluation assumes Laravel 10 or 11 with Filament v3, but you should confirm the actual Composer constraint before adopting. The 1.x line is early, and dependabot-driven dependency bumps mean you should pin the package and run composer why-not against your target Filament version. Treat Filament major-version compatibility, including v4, as something to verify rather than assume.
- Does filament-teams work with an existing teams table or tenancy setup?
- It can collide with pre-existing teams and team_user tables, so diff the published migrations against your current schema before running them. The plugin is a good fit for greenfield Filament panels that need team-scoped resources, but a weaker fit if you already use Stancl, Spatie multitenancy, or hand-rolled team_id scoping. In those cases it risks becoming a second source of truth for tenancy.
- Is filament-teams compatible with spatie/laravel-permission?
- The package documentation in this context does not explicitly state its role and permission model, so compatibility with spatie/laravel-permission or Bouncer must be verified. Team plugins often overlap with existing role models, which is a common source of integration friction. Review how the plugin assigns roles and whether it ships its own team model before combining it with another permission package.
- How do team invitations and member roles work in filament-teams?
- The plugin adds team and membership management to Filament panels, including creating teams, inviting members, and assigning roles through an admin interface. It integrates with Laravel models and permissions so team resources can be scoped per team. Exact invitation flow, role definitions, and middleware behavior should be confirmed against the package source for your version.
- How do I register the filament-teams plugin in a panel provider?
- Register the plugin inside your Filament panel provider, typically in the panel configuration chain alongside your other plugins after installing the package. You also need to publish and run migrations and configure your User model for the team contract the plugin expects. Test the registration in a non-production panel first to confirm tenancy scoping behaves as intended.
- Does filament-teams include translations for non-English admin panels?
- Yes, version 1.2.0 added 17 new locales, covering major markets such as ar, de, es, fr, ja, nl, pl, pt, ru, tr, uk, and zh_CN. Locale files are additive and fall back to English, so untranslated keys should remain safe. Some languages, for example ko, id, and vi, are not included, so confirm the fallback is acceptable for your users.
- Is filament-teams safe for production, and does it test tenancy isolation?
- The 1.2.0 release itself is low risk because it only adds translations and standardizes CI, with no schema, API, or behavioral changes. The broader package carries more risk as a single-maintainer, early 1.x project, and you should verify whether there is test coverage for cross-team data leakage before production use. Validate isolation in staging with at least two teams and seed roles before enabling tenancy scoping.
- What changed in filament-teams 1.2.0 and is it a breaking change?
- Version 1.2.0 is an additive patch: it adds 17 new locales and standardizes the CI workflow, with no schema, API, or behavioral changes. No migration or config changes are required, so it can be treated as a drop-in update from 1.1.0. It does not change the package architecture or its Filament plugin role.