Sentry Discover filters: limits of persisted queries across projects and sessions

I'm designing a team workflow around Sentry's Discover query builder and need to understand the boundaries of its filter persistence before committing to it. My goal is to share a standardized set of saved filters (by status, logger, and culprit) across an entire engineering team without each member rebuilding them manually.

From what I can tell, Discover filter selections survive page reloads and URL changes for an individual user, but the documented behavior is unclear on several edges: whether persistence is scoped per project or per organization, whether it applies to incognito or cleared-storage sessions, and whether saved queries propagate to teammates or remain strictly personal.

I'm also unsure how persistence interacts with the Projects dashboard, where tab order and keyboard navigation follow WCAG 2.1 AA, since some of our users navigate by keyboard alone and I want to confirm filter inputs are reachable and retain state in that flow.

Specifically: are Discover filter selections stored server-side per user, or only in local browser state? Can a saved Discover query be shared organization-wide, or must each user recreate it? Does filter persistence behave identically across projects within the same organization?