- What does mominalzaraa/filament-team-guard actually do?
- It bridges Laravel Jetstream's team model into Filament panels so users can be assigned to teams, switch their active team, and have Filament resources, pages, and queries automatically scoped to the current team. It is an enhanced Laravel starter kit built with Filament and inspired by Jetstream, and it also covers auth features such as two-factor authentication, passkeys, and API tokens. It is aimed at secure multi-tenant admin panels where each team should only see its own data.
- How do I install filament-team-guard in a Laravel application?
- Install it with Composer using composer require mominalzaraa/filament-team-guard, then follow the README for publishing configuration and action classes and for registering the Filament plugin in your panel provider. The package assumes a Laravel application with Jetstream teams enabled and Filament installed. Check the README for any required migrations or assets, since v2.1.1 itself introduces no migrations or config schema changes.
- Which Laravel, Filament, Jetstream, Livewire, and PHP versions are supported?
- The package's own Composer constraints and README are the source of truth for supported Laravel, Filament, Jetstream, Livewire, and PHP versions. The technical assessment flags the compatibility matrix as an open question, so verify Filament v3 versus v4, the Jetstream major version, Livewire v3, and PHP 8.2+ before adopting it. Applications running Filament without Jetstream teams, or Jetstream in personal-account-only mode, are out of scope.
- Does filament-team-guard work without Jetstream teams enabled?
- No. The package is designed to bridge Jetstream's team model into Filament, so it expects a Laravel application with Jetstream teams enabled. Applications running Filament without Jetstream teams, or Jetstream configured in personal-account-only mode, are explicitly out of scope. If you need team scoping without Jetstream, plan for adaptation rather than configuration.
- How does team scoping work for Filament resources and pages?
- Users switch their active team, and the package scopes Filament resources, pages, and queries so each team sees only its own records. The package follows framework conventions, so the integration cost is mostly configuration rather than custom adaptation. Always test custom queries, relationship managers, widgets, and global scopes for tenant isolation before relying on it in production.
- Is filament-team-guard a replacement for Laravel Jetstream?
- No. It bridges Jetstream's team model into Filament panels and reimplements or overrides some Jetstream team-management Livewire UI, but Jetstream remains the underlying team and authentication layer. It is inspired by Jetstream and is positioned as an enhanced Filament starter kit rather than a standalone replacement. Expect to keep Jetstream installed and configured with teams enabled.
- Does it support two-factor authentication, passkeys, and API tokens?
- Yes. The package overview describes team management plus auth features including two-factor authentication, passkeys, and API tokens. These capabilities are part of the enhanced starter-kit experience built around Filament. Verify the exact versions and configuration requirements in the README before planning your authentication rollout.
- How do I customize team name updates with my own action class?
- The package supports publishable action classes under the App\Actions\FilamentJetstream namespace, mirroring Jetstream's own App\Actions\Jetstream convention. Your Livewire component should resolve the UpdatesTeamNames contract from the Laravel container so a published and customized UpdateTeamName action is honored. v2.1.1 restores this behavior and adds integration tests covering both default and custom container bindings.
- What changed in v2.1.1 and should I upgrade?
- v2.1.1 fixes a container-dispatch bypass where UpdateTeamName called $team->update() directly instead of resolving the UpdatesTeamNames contract, which caused published custom actions to be silently ignored. The patch restores the documented Laravel extension pattern and adds integration tests for default and custom bindings. There are no migrations, config schema changes, or removed APIs, but because previously dead container rebinds can now become live, pin to 2.1.1, update on a branch, and grep for existing UpdatesTeamNames bindings.
- Does the guard enforce Laravel authorization policies for team switching and access?
- That is not evidenced in the release notes, which cover team naming only. Before treating it as a security boundary, verify whether the guard behavior calls authorize() and Laravel policies, or whether it maintains a parallel permission model. Add tests for team switching, team access, and tenant isolation, and review the source if authorization correctness is critical.