Filament Team Guard Laravel Package

Product Decisions This Supports

• Build vs. buy for team administration: If you are building a Laravel/Filament SaaS with Jetstream-style teams, this package can provide the team-management surface in the admin panel instead of custom Filament resources for team listing, naming, and guard-related workflows.
• Extensibility vs. hard-coding: The v2.1.1 fix makes the UpdateTeamName Livewire component honor the UpdatesTeamNames contract rather than calling $team->update() directly. That lets product teams ship custom rename workflows—approval queues, audit logging, naming policies, domain-specific validation—without forking the package.
• Roadmap sequencing: Treat team lifecycle management as a platform capability. Use package defaults for an initial release, then replace or extend behavior through published actions and contracts as product rules mature.
• Upgrade risk management: The added integration and regression tests, plus isolated SQLite test configuration, reduce the chance that package upgrades silently break custom team actions. This matters when team renaming touches onboarding, billing, or compliance flows.
• Admin UX decisions: Supports decisions about where team management lives—Filament admin versus end-user settings—and how much customization is exposed to operations teams.

When to Consider This Package

Consider it when:

• You are on Laravel + Filament and use Jetstream-style teams or a similar team/tenant model.
• You need an admin-facing team-management UI quickly and prefer convention over custom CRUD.
• You require a supported customization seam for team renaming through the UpdatesTeamNames contract and published App\Actions\FilamentJetstream\UpdateTeamName classes.
• You value active maintenance: this patch restores respect for custom published actions and adds regression coverage.

Look elsewhere when:

• You are not using Filament, or your tenancy model diverges significantly from Jetstream teams.
• You need enterprise-grade authorization, SSO/SCIM, audit/compliance features, or complex hierarchical permissions out of the box.
• You need a large ecosystem with extensive documentation and long-term support guarantees; validate package maturity and maintainer bandwidth first.
• Your team rename logic cannot be expressed through the provided contract and requires deep changes to the Livewire component itself.

How to Pitch It (Stakeholders)

For executives: This package can shorten delivery of team management in our Filament admin panel and reduce bespoke code. The latest patch is a positive maintenance signal: it fixes a customization regression so our published team-rename actions are respected again, and it adds tests. That lowers upgrade risk and means we can adapt team workflows—audit, approvals, naming rules—without forking.

For engineering: v2.1.1 corrects UpdateTeamName to delegate to the UpdatesTeamNames contract instead of calling $team->update() directly, restoring custom App\Actions\FilamentJetstream\UpdateTeamName behavior. Integration and regression tests plus isolated SQLite configuration improve confidence. Adopt if we are already on Filament/Jetstream; keep custom rename logic behind the contract and pin versions until our published actions are validated against the package test suite.