# No search bar for some collections

**URL:** <https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198>\
**Category:** Help me!\
**Created:** [June 24, 2025, 1:16pm UTC](https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198 "2025-06-24T13:16:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nico\_lrx](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/nico_lrx/32/708_2.png) [@nico\_lrx](https://community.forestadmin.com/u/nico_lrx)\
**Post date:** [June 24, 2025, 1:16pm UTC](https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198/1 "2025-06-24T13:16:43Z")

</div>

## Feature(s) impacted

Search bar in dashboard.

## Observed behavior

In the dashboard, the search bar is not displayed for some of my collections.

 ![Capture d’écran 2025-06-24 à 15.12.45](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/6/646310c14f9ead849431de7ee54ae65649043a4f.png)

## Expected behavior

The search bar should appear for all collections.

## Failure Logs

Console logs:

 ![Capture d’écran 2025-06-24 à 15.15.24](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/6/6c5061fe621f887cf34378fc0633344cd1f69485.png)

No failure logs in the web app logs.

## Context

- Project name: francaisavecmarcel
- Team name: operations
- Environment name: development/production
- Database type: postgresql
- Recent changes made on your end if any: NA

**And, if you are self-hosting your agent:**

- Agent technology: (nodejs, php, ruby, python) : ruby / ruby on rails
- Agent (forest package) name & version (from your .lock file): forest\_liana gem v9.14.4

---

<div class="post-metadata">

**Author:** ![matthv](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/matthv/32/3269_2.png) [@matthv](https://community.forestadmin.com/u/matthv)\
**Post date:** [June 24, 2025, 2:05pm UTC](https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198/2 "2025-06-24T14:05:35Z")

</div>

Hello @nico_lrx

You can bring the search bar back by explicitly adding `is_searchable: true` to your collection definition. For example:

```javascript
class ForestLiana::Collections::User
  include ForestLiana::Collection

  collection :User, is_searchable: true

end

```

Let me know if you have any questions!

---

<div class="post-metadata">

**Author:** ![nico\_lrx](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/nico_lrx/32/708_2.png) [@nico\_lrx](https://community.forestadmin.com/u/nico_lrx)\
**Post date:** [June 24, 2025, 2:12pm UTC](https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198/3 "2025-06-24T14:12:18Z")

</div>

> [@matthv](#):
>
> `collection :User, is_searchable: true`

That worked, thanks! Is it possible to set is\_searchable: true by default to all collections?

---

<div class="post-metadata">

**Author:** ![matthv](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/matthv/32/3269_2.png) [@matthv](https://community.forestadmin.com/u/matthv)\
**Post date:** [June 24, 2025, 2:25pm UTC](https://community.forestadmin.com/t/no-search-bar-for-some-collections/8198/4 "2025-06-24T14:25:15Z")

</div>

It’s not possible to enable `is_searchable: true` globally by default for _all_ collections, but there’s a simple workaround you can use by creating a small base class and inheriting from it in your custom collections.

Here’s how:

Create a shared base collection class (`lib/forest_liana/collections/forest_collection.rb`)

```javascript
class ForestLiana::Collections::ForestCollection
  include ForestLiana::Collection

  def self.collection(collection_name, opts = {})
    opts[:is_searchable] = true unless opts.key?(:is_searchable)
    super(collection_name, opts)
  end
end

```

Then use it in your collection definitions

```javascript
class ForestLiana::Collections::User < ForestLiana::Collections::ForestCollection
  collection :User

  ...
end

```

With this setup, `is_searchable` will be `true` by default unless you override it explicitly.

Let me know if you’d like help setting that up!