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

# Email search

Sometimes you need to look for an email yourself: a message an employee reported, a sender you are wary of, or a mail you want to trace across mailboxes. You can search your employees' mailboxes directly from Stoïk Protect, with no need to contact us.

{% stepper %}
{% step %}

## Open the search

In Stoïk Protect, go to `Email Security` > `Suspicious emails`, then open the **Search an email** tab.
{% endstep %}

{% step %}

## Enter your criteria

You can combine several of them:

* the email address of the sender or the recipient;
* the display name of the sender;
* the subject;
* a timeframe: the last 7 days, the last month, or a custom period.
  {% endstep %}

{% step %}

## Launch the search

Start the search and follow the results as they appear.
{% endstep %}
{% endstepper %}

## Read the results

* Results appear as the search runs. The first ones show up as soon as they are found, so you do not have to wait for the full search to finish.
* Click a result to open a preview of the email's content.
* The search keeps running in the background. You can switch tabs and come back to it later.

## Permission

Access to the search is controlled by a dedicated permission: **Search for an email**, under **Cyber: Managed Services**. It is unchecked by default, because reading employees' emails is more sensitive than reviewing suspicious alerts. Only people who are explicitly granted this permission can read emails.

{% hint style="info" %}
If you cannot see the tab or run a search, ask the person who manages permissions on your account to grant it to you.
{% endhint %}


---

# 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://docs.stoik.io/email-security/email-search.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.
