- How do I install TeamKit v4 in a Laravel 13 app?
- Install TeamKit v4 with Composer using jeffersongoncalves/teamkitv4, then follow the package publish and migration steps for config, migrations, and Filament resources. On 4.14.0 and later, Composer should also pull the separate user and admin packages that now provide models, resources, and login. For an existing app, install on a branch first rather than directly in production.
- Does TeamKit v4 support Laravel 13 and Filament 4?
- TeamKit v4 is built for Laravel 13.x and Filament 4.x. Release 4.14.0 bumps Filament to v4.14.0, so the core admin panel should be compatible with that minor line. If you use third-party Filament plugins, verify each plugin supports Filament v4.14 before upgrading.
- Can TeamKit v4 handle multi-tenant team management?
- TeamKit v4 is aimed at adding multi-tenant team management to a Laravel application, with teams as the organizing boundary for users. It ships ready-made models, migrations, and workflows for teams and memberships, plus Filament admin resources intended to be team-scoped. Review the published team scoping and policies against your own tenancy rules before relying on it.
- How do team invitations work in TeamKit v4?
- TeamKit includes an invitation workflow for adding users to teams, with models and migrations supplied by the package. You will still need to configure Laravel mail and review the published invitation resources so the flow matches your onboarding and notification requirements. Test invitation acceptance, expiry, and duplicate-invite behavior in a non-production environment.
- How are roles and permissions handled in TeamKit v4?
- Roles and permissions are part of TeamKit's team membership model, with migrations and Filament resources provided for administration. Because authorization is security-sensitive, review the published migrations, policies, and gates rather than assuming defaults match your access model. If you need fine-grained abilities, confirm how TeamKit's roles map to your application's policies before customizing.
- How should I test TeamKit v4 team, invitation, and permission flows?
- For testing, use a fresh Laravel 13 test database and cover team creation, membership changes, invitations, role assignment, and tenant scoping. Since 4.14.0 moved User and admin resources into separate packages, include auth/login and Filament resource access tests rather than only model tests. Run the suite against the exact Filament v4.14 and package versions you plan to deploy.
- How do I upgrade TeamKit v4 from 4.13.x to 4.14.0?
- There is no documented migration guide in the 4.13.x to 4.14.0 release notes, so treat the upgrade as a spike rather than a routine patch. Branch your app, update the package, then diff published User and Admin models, Filament resources, login routes, and migrations against what 4.14.0 expects. Re-run auth, team scoping, invitation, and role tests before merging.
- Is TeamKit 4.14.0 a breaking change for custom User models or login?
- Possibly. Release 4.14.0 moved user and admin concerns, including models, resources, and login, into separate packages consumed as dependencies, but the changelog does not explicitly list breaking changes. If you customized the bundled User model, login page, guard, redirects, SSO, MFA, or rate limiting, assume your changes are in a merge or overwrite path until verified. A representative install and auth test is required before upgrading production.
- Is TeamKit v4 production-ready for a new Laravel and Filament project?
- For greenfield Laravel 13 and Filament 4 projects, TeamKit v4 can be a practical starting point because the team, membership, invitation, role, and permission pieces are pre-wired. For production, pin versions, review lockfile changes, and monitor the new user/admin packages because 4.14.0 expands the dependency surface. The package version also tracks Filament's version, which makes API stability harder to infer from the version number alone.
- What are alternatives to TeamKit v4 for Laravel team management?
- Alternatives depend on whether you want a Filament starter kit or a general Laravel team scaffold. Laravel Jetstream provides team scaffolding without Filament, while Filament's native tenancy plus a permissions package can be assembled manually. TeamKit's differentiator is the ready-made models, migrations, and team-scoped admin resources for Laravel 13 and Filament 4.