# Add Favourite Views section to Quick Search **URL:** \ **Category:** Ideas & Features\ **Created:** [February 8, 2022, 1:20pm UTC](https://community.fibery.io/t/add-favourite-views-section-to-quick-search/2510 "2022-02-08T13:20:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [February 8, 2022, 9:52pm UTC](https://community.fibery.io/t/add-favourite-views-section-to-quick-search/2510/2 "2022-02-08T21:52:55Z")
This sounds more like a function for a “quick switcher” or “command palette”, although some tools do combine quick switch and search into one as they have some overlap in utility. From a UI standpoint though I am not sure how favorites would sensibly show up on the search window in Fibery. > **[How to build a remarkable command palette](https://blog.superhuman.com/how-to-build-a-remarkable-command-palette/)** > > Command palettes are incredible tools: they're fast, versatile, and will transform users into power users! Tim Boucher explains how to build a truly remarkable command palette for your product... Personally I would love to see either a dedicated quick switcher/command palette, or perhaps some new _functional_ syntax for the quick search that allowed you to filter search very quickly to particular areas. So for example a special symbol preceding some 1-2 letter command or filter indicator, and then regular search text. E.g. `=fa dail` would limit search to _favorites_ (=fa) and “dail” would match “daily tasks”. This has the benefit of keeping the search UI focused on search, but also addresses your need, and in a way that stays keyboard-centric for those who prefer that. It could also ultimately become much more powerful and tie-in with other recently discussed search needs e.g.: > [@Filter search results based on Field Values](https://community.fibery.io/t/filter-search-results-based-on-field-values/1052): > > The more I actually use Fibery day-to-day, the more tasks I complete, and the more “closed” entities I end up with. Yet they all still show up in my searches. This really limits the usefulness of search at times, whether in the Ctrl-K pop-up or in-line entity linking (this is even more of an issue due to [Narrow texts in entity search pop-up make correct selection difficult](https://community.fibery.io/t/narrow-texts-in-entity-search-pop-up-make-correct-selection-difficult/1051). I’m not sure the best way to handle this. I know the “status” is a feature of the Workflow Extension. It seems important e… So for example I could filter by database entities `=db searchterm` vs. views `=vi searchterm`. Obviously the special character would have to be something unique that is unsupported in entity names, or have some other way of delineating it. But I like this core concept, at least… --- _[View the full topic](https://community.fibery.io/t/add-favourite-views-section-to-quick-search/2510)._