> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/search-cockpit/readme.md).

# Search Cockpit

Use the Search Cockpit to manage search indexes for custom instances, run searches, and reuse saved searches.

{% hint style="danger" %}
This feature is currently in preview mode and is not fully functional yet. Some capabilities may be incomplete or subject to change. If you have any questions, contact the [Emporix Support Team](mailto:support@emporix.com).
{% endhint %}

{% hint style="warning" %}
The Search Cockpit is not enabled by default. To request access and have Emporix configure and prepare the initial setup for your tenant, contact the [Emporix Support Team](mailto:support@emporix.com).
{% endhint %}

The **Search Cockpit** is a Management Dashboard perspective for finding custom instances of a schema type. A custom schema type (custom entity) defines the fields for those instances. You define a search index for the fields you need, wait until the index is ready, then search those instances by text or by exact values. A saved search keeps the index, filters, and query settings so you can run the same search again with different text.

After Support enables the cockpit on your tenant, open it from the Management Dashboard [perspective chooser](/user-guides/management-dashboard/administration/perspectives.md). Choose the **Search Cockpit** perspective.

Your tenant must have custom schema types. Without them, the cockpit cannot list types or create indexes. Create types and instances in [Custom Entities](/user-guides/management-dashboard/settings/custom-entities.md) and [Custom Instances](/user-guides/management-dashboard/custom-instances.md) first.

## Cockpit views

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><i class="fa-list">:list:</i></td><td align="center"><strong>Indexes</strong></td><td align="center">Create and manage search indexes, follow build jobs, and export or import index configuration.</td><td><a href="/search-cockpit/indexes.md">Indexes</a></td></tr><tr><td align="center"><i class="fa-magnifying-glass">:magnifying-glass:</i></td><td align="center"><strong>Search</strong></td><td align="center">Choose a schema type and a ready index, build queries and filters, and run a search.</td><td><a href="/search-cockpit/search.md">Search</a></td></tr><tr><td align="center"><i class="fa-bookmark">:bookmark:</i></td><td align="center"><strong>Saved searches</strong></td><td align="center">Store a search definition and open it again with new query text.</td><td><a href="/search-cockpit/saved-searches.md">Saved searches</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/search-cockpit/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.