Weave Code
Filament Invite Laravel Package
concept7/filament-invite
A Filament plugin for inviting users to your panel. Send email invitations, generate secure signed links, track pending invites, resend or revoke them, and assign roles or permissions when invitations are accepted—all from a simple Filament resource.
At a glance
Frequently asked questions about Filament Invite
- How do I install concept7/filament-invite in a Laravel app?
- Install it with Composer using composer require concept7/filament-invite. Then publish the package config and migrations, run your migrations, add the invitation trait to your User model, and register the plugin on the Filament panel where invitations should be managed. Re-run your auth and invitation tests after wiring it in.
- Which Laravel and Filament versions does concept7/filament-invite support?
- v2.0.2 explicitly adds Laravel 13 compatibility, and the package is positioned for Filament-based admin apps on Laravel 11, 12, and 13. Because Laravel 13 support landed as a widened Composer constraint in a patch release, verify the full resolution set includes a compatible Filament major and mail stack. Check the package's composer.json and CI for the exact supported version matrix rather than assuming backward compatibility with Laravel 10.
- How does the invitation flow work in Filament?
- A Filament resource lets you send email invitations that contain secure signed links. The package tracks pending invitations and supports resending or revoking them before acceptance. When the invited user accepts and registers, the plugin can assign configured roles or permissions.
- Is v2.0.2 a breaking change from v2.0.1?
- No. v2.0.2 is a single-change release that widens the Laravel constraint for Laravel 13; the TPM assessment describes it as a compatibility patch with no declared API, config, migration, or UI changes. From v2.0.1, update the constraint, run composer update concept7/filament-invite, and re-test the full invitation flow. Upgrading from v1.x is different: treat it as a major upgrade and read the v2.0.0 notes because v2.0.2 does not enumerate the v2 breaking changes.
- Can I assign roles or permissions when an invitation is accepted?
- Yes. The plugin supports assigning roles or permissions when an invitation is accepted, configured as part of the invitation workflow. Confirm the roles and guards you assign match the panel's auth guard and your User model's role setup. Test acceptance with each role to ensure the assignment happens before the user reaches protected panel pages.
- Does it work with multiple Filament panels or different auth guards?
- The plugin is a thin Filament panel plugin, so it fits best when one panel and one consistent auth guard own the invitation workflow. The TPM assessment flags multi-panel setups with divergent auth guards as a poor fit. If you need cross-panel invitations, plan to customise the resource and token acceptance logic, and test guard switching explicitly.
- How are invitation tokens secured and expired?
- The package generates secure signed links for invitations, and pending invites can be resent or revoked. The public release notes do not publish token entropy, expiry defaults, or a CVE history, so review the config and source for expiry and single-use behaviour before production. Align its token handling with your password-reset standards and add tests for expired, reused, and revoked links.
- How do I test invitation emails locally and in staging?
- Run the flow locally with a mail sandbox such as Mailpit or the log mailer, then repeat in staging with mail sandboxing before production. Test issuing, email delivery, token acceptance, expiry, re-invite, and revocation. On CI, install from a clean image to catch Composer constraint conflicts that a widened Laravel constraint could mask.
- What are the alternatives to concept7/filament-invite?
- Alternatives include building a custom Laravel signed-URL invitation flow, using starter kits such as Breeze or Jetstream where team invitations are built in, or managing Filament users manually with a custom resource. Choose concept7/filament-invite when you want the invitation UI, pending tracking, resend/revoke, and role assignment inside Filament without building that resource yourself. If you do not use Filament, a framework-native or custom approach is usually a better fit.
- Is concept7/filament-invite actively maintained and production-ready?
- It is usable in production for Filament-centric Laravel apps, but the maintenance model is community-driven with a small contributor base. Laravel 13 support arrived in a patch release via a widened Composer constraint, which suggests tracking each Laravel and Filament major is necessary rather than assuming passive stability. Pin the version explicitly, review release notes at each framework upgrade, and keep invitation flow tests in CI.
Weaver
How can I help you explore Laravel packages today?