> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/faq/glpi/saved_searches.md).

# Saved searches

***

{% embed url="<https://www.youtube.com/watch?v=usV0WY3S0qE>" %}

### What is a saved search?

A saved search allows you to display the results of a query without having to specify filters for each search.

{% hint style="success" %}
**Example**

Display all open tickets for which the [TTR ](#user-content-fn-1)[^1]has been exceeded
{% endhint %}

This function is available for tickets, problems, changes, computers, network hardware, etc.

***

### How do I set up a saved search?

If we want to see, for example, all unresolved tickets whose [TTR ](#user-content-fn-1)[^1]has expired, we need to start by performing the correspondingsearch. Once you have done this, click on :star:

![Alt text](/files/lkwh1F3druBPNVC0gOjd)

A new menu will appear, allowing you to set the various options available:

* **`Do count`**: displays the number of items found next to the saved search,
* **`Visibility`**: allows you to make a search public or private.
* **`Entity`**: defines the entity where the search should appear,
* **`child-entities`** : defines the visibility of child entities.

***

### Can a saved search be public?

Yes, you just need to define it when you save the search.

***

### Why isn't my public search visible to other profiles?

The search can only be visible if the authorisations in the corresponding profile have been granted (**`Administration`** > **`Profiles`**. Choose the relevant profile and then the tools tab)

{% hint style="warning" %}
Users with a simplified interface do not have access to public saved searches.
{% endhint %}

***

### Where can I find my saved searches?

You can find them in 2 places:

* In the **`lists`** menu of the corresponding item
* In **`Tools`** > **`Saved searches`**.

***

### What is the purpose of alerts on saved searches?

Alerts allow you to send notifications when any of your searches exceed a quota. Alerts can be sent to the administrator, entity administrator, specific profile(s), specific group(s) or group supervisors.

{% hint style="success" %}
**Example**

If more than 5 unresolved tickets have exceeded the closing time imposed by a TTR[^1], a notification will be sent.
{% endhint %}

***

### How do I set up an alert on a saved search?

In the **`Alerts on saved searches`** section of your saved search, click **`Add an alert`** (or **`Create it now`** if the notification doesn't exist). GLPI will create a new notification. All you have to do is set it to **`Active`**, add a **`Template`** and add the **`Recipients`** of the notification.\
\
A complete tutorial is available here: <https://help.glpi-project.org/tutorials/notifications/alert_glpi#set-up-an-alert-for-a-saved-search>

[^1]: Time To Resolve


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.glpi-project.org/faq/glpi/saved_searches.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.