# Saved Searches

GLPI offers a system for saving searches (bookmarks). Once the search is done, it is possible to save it from a star-shaped button accessible in the search form.

<div align="left"><img src="/files/3kiRCICqfiYER6xUbR6M" alt="Saving a search"></div>

There are two types of saved searches:

* *Private* searches: Usable by all users and they are only accessible by their author
* *Public* searches: Can only be created by authorized users and are accessible by all users provided they belong to the configured entities

Saved searches can be accessed by clicking on the star shaped button in the user menu.

<div align="left"><img src="/files/ZG9HNgOpqiCF41Hz02GU" alt="List of saved searches" width="305"></div>

From this interface, it is possible to:

* Reorder private searches (drag & drop) - public searches use automatic sorting
* Select a default search (only one possible per type of object) by clicking on the star icon
* Access the search results (by simply clicking on it)
* Access the saved searches management interface, by clicking on the wrench icon at the top right

{% hint style="warning" %}
Setting a particularly heavy search as the default display can have catastrophic effects on the overall performance of the application!
{% endhint %}

## Display of counters

The GLPI settings are used to define whether the counters should be displayed or not. In the case of research, it's a bit more complicated.

This is because some searches can take a long time (and resources) to complete. In order to limit the impact on performance, the heaviest requests are not counted by default. So that the execution time of a saved query can be calculated; it must be executed at least once. A scheduled task is also offered to calculate execution times regularly (and thus avoid requests that would have become heavy over time).

Administrators can override the automatic count method, and have a search always or never be counted. This possibility should be used sparingly.

## Configuring alerts

It is possible to configure the sending of "alerts" on a saved search using the GLPI notification system . Sending a notification is based on the number of results returned by the search, compared with the chosen operator to the entered value.

![Configuration of alerts on saved searches](/files/aODKJr2g3LlcPU0t3mQJ)

The notification(s) used are displayed for reference from the alerts configuration tab. For private research; only the user who created the search can be notified, using a template provided by default; in this case, a single notification will be linked.

For public searches, a specific event must be created, as well as a notification that uses it. This is only possible from the alerts configuration tab.

Once the specific notification is created, it has to be configured by associating it with a template and by selecting the desired recipients. Note that it is possible to associate several notifications with the same search via the event that corresponds to it.

{% hint style="info" %}
As long as the notification specific to a public search is not created; it will not be possible to add alerts.

<img src="/files/CrQvB552tdljl3QsvrlE" alt="No saved search notification message" data-size="original">
{% endhint %}


---

# Agent Instructions: 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/documentation/readme-1-1/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.
