> 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/saved-searches.md).
# Saved searches
Store a search definition for a schema type and index, then open it again with new query text.
The **Saved searches** view keeps a search definition so you can run the same index, filters, and query settings again with different text. Saving a search does not rebuild the index.
## Browse saved searches
Open **Saved searches** from the side menu. Use the filters above the list to narrow down the results and find what you need. You can show all schema types or limit the list to one type.
Select **Use** to open [Search](/search-cockpit/search.md) with that definition. Select **New saved search** to create one from this list.
Saved searches list
## Create a saved search
{% stepper %}
{% step %}
#### Open the create form
On **Saved searches**, select **New saved search**. If the list is already filtered to one schema type, that type is selected on the form. If the list shows **ALL**, choose **Schema type** on the create screen.
{% endstep %}
{% step %}
#### Enter details and criteria
Provide **Id**, **Name**, and an optional **Description**. Choose the **Index** for that schema type, then add the same kind of queries and filters you use on Search.
{% endstep %}
{% step %}
#### Save
Select **Save**. If the id already exists, confirm whether to replace it.
{% endstep %}
{% endstepper %}
You can also create a saved search from the Search view with **Save search** after you build criteria there. Both entry points store the same kind of saved search.
## Edit, use, or delete
Open a saved search from the list to change its details or criteria, then save. Use **Use** to open Search with the definition loaded. To remove a saved search, use **Delete** and confirm.
---
# 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/saved-searches.md?ask=&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.
