The Chat and Search filters applied by users aren’t sticky/persistent at this stage. This is resulting in users applying filters before they use Glean to Search or Chat, which is increasing friction.
This feature request is to propose that individual users in an instance be allowed to save defaults for Search and Chat alike, not at the org/instance level but at the user level i.e., multiple users on the instance can have one or more saved filters for Chat or Search. This removes the friction and allows the users to Chat or Search using their preferred defaults.
The saved filter should load by default when the user that saved the filter loads their Chat or Search page.
Customer specific use case:
- A user finds a datasource spammy and impacting chat/search results. So, they'd like to avoid having it included in chat by default.
- This feature request--if implemented--should allow their users to apply and save filters for all future Chat or Search sessions, reducing friction.
This feature request is internally tracked using FR-4024.
