# \[DONE\] Ability to hide some databases from search/Entity # Link by default

**URL:** <https://community.fibery.io/t/done-ability-to-hide-some-databases-from-search-entity-link-by-default/4442>\
**Category:** Ideas & Features\
**Tags:** search\
**Created:** [May 13, 2023, 1:39am UTC](https://community.fibery.io/t/done-ability-to-hide-some-databases-from-search-entity-link-by-default/4442 "2023-05-13T01:39:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [June 1, 2023, 4:30am UTC](https://community.fibery.io/t/done-ability-to-hide-some-databases-from-search-entity-link-by-default/4442/8 "2023-06-01T04:30:56Z")

</div>

Hi all,

Just came across this and here is the use case that I had written up and was about to post:

**Please note** : I would like to have some ability to define which spaces will show this search and which don’t, not just a blanket “show/hide” option.

> Ability to limit search visibility of a database entity. What I mean is limiting where an entity (database entry) appears in the search when I press `#`.
> 
> 1. **Global** : Appears everywhere
> 2. **Specific spaces** : Select spaces where it should appear
> 3. **Same space only** : Only in the same space
> 4. **Link only** : Only way to link to it is using the URL and a link
> 
> We have by now almost 100 databases and a lot of spaces that we navigate across. As a small team, we touch on many places and I prefer structured information rather than tables and tables to lists. Simple example is a glossary: I’d rather make it a database than just a table on a page as it allows me to sort/group/filter and embed info. Now obviously, I wouldn’t want a term to appear in the search every time I enter #…
> 
> On top of that, there are many entities that are just relevant in one or few spaces. For example:
> 
> 1. User Stories generally should only be linked to in the product management space
> 2. Features or Screens, however might be referred to across product management, user research and design, etc.
> 3. Clients should only be visible in some spaces
> 4. Product Releases should hue visible everywhere as they are a central piece for everybody’s planning
> 
> As you can imagine, the linking search field has become very cumbersome for us despite the heuristics you apply. Being able to define visibility on a database would solve this massively.

Thanks!

---

_[View the full topic](https://community.fibery.io/t/done-ability-to-hide-some-databases-from-search-entity-link-by-default/4442)._