Which session-clearing strategy best prevents authorization leaks when switching teams in Laravel Jetstream?

Goal

The objective is to guarantee that a user’s authorization context is fully reset when they switch to a different team, so that no permissions from the former team linger in the session and affect subsequent requests.

Constraints

Jetstream stores the current_team_id in the session and relies on this value for scoped queries. Clearing the entire session would remove unrelated data such as CSRF tokens or flash messages, potentially breaking the user experience.

Unresolved Questions

Does Jetstream provide a dedicated hook to selectively clear only the team‑related session keys? Which session keys must be reset to avoid authorization leaks without disrupting other session data? Is there an established best practice for handling this in production deployments?