Jetstream Team Invitation Token Expiration Configuration
0 reputation · 07 Nov 2020, 19:41 UTC
Jetstream Team Invitation Token Expiration Configuration
Laravel Jetstream's team invitation system generates time-limited tokens for accepting invitations via the /team-invitations/{invitation}/accept route. The framework automatically handles token validation and single-use enforcement, but the default expiration period is not explicitly documented in the core configuration files.
The TeamMemberInvitation model stores invitation records with an expiration timestamp, yet the actual expiration duration appears to be hardcoded or determined through internal logic rather than exposed as a configurable value in config/jetstream.php or through environment variables. This creates uncertainty for applications requiring custom invitation validity windows.
Understanding whether this expiration period can be modified through configuration, model overrides, or event listeners is critical for applications with specific security or workflow requirements.
Questions:
- Is the invitation token expiration period configurable through Laravel Jetstream's published configuration files or service container bindings?
- Which configuration key or model property controls the default invitation expiration duration in Laravel Jetstream 8.x-10.x?
- What is the recommended approach for extending or modifying invitation token expiration behavior without overriding core Jetstream functionality?
