> 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/human-security/report-button/employee-guide.md).

# Employee guide

Your IT team works with Stoïk to protect the company from cyberattacks. The Report button lets you flag any email that looks suspicious, so your IT team can act on it.

If an email looks suspicious (unusual sender, urgent tone, unexpected attachment, link asking you to log in), the safest thing to do is to **report it instead of clicking, replying, or deleting it**.

<div><figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FCuzgvs9uHbNjDFVg8wdr%2FScreenshot%202026-06-09%20at%2015.18.31.png?alt=media&amp;token=22591f2b-4bac-4363-bb9a-68c81258a654" alt=""><figcaption></figcaption></figure> <figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FfU8yclm1Hyf566NWaol0%2FScreenshot%202026-06-09%20at%2015.19.01.png?alt=media&amp;token=5e9b17c8-02ac-48cb-bcf4-c36fda43f2ee" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
The button works in Outlook (desktop app and web) and in Gmail on Chrome-based desktop browsers (Chrome, Edge, Brave, and other Chromium browsers). It is not available on mobile, or in Gmail on Safari or Firefox.
{% endhint %}

## Report an email

{% tabs %}
{% tab title="Outlook" icon="microsoft" %}

1. Open the suspicious email.
2. In the email toolbar, click **Report Phishing**.
3. Confirm the report.
   {% endtab %}

{% tab title="Gmail" icon="google" %}

1. Open the suspicious email.
2. At the top of the email, click the **Stoïk Report** icon.
3. Confirm the report.
   {% endtab %}
   {% endtabs %}

A confirmation message appears right away.

## After you report

* **If the email was a phishing simulation** sent by your IT team: you see a short message explaining the warning signs you spotted.
* **Otherwise**: the email is forwarded to your IT or security team for review. If your company has turned on verdict notifications, you receive an email with the result.

The email stays in your mailbox as is. You don't have to do anything else.

{% hint style="info" %}
**In doubt? Always report.** Reporting a legitimate email by mistake has no consequence. Clicking on a real phishing email can compromise the whole company.
{% endhint %}

## Install the button yourself

In most cases, your IT team has already added the button to your mailbox. If you don't see it, install it in two minutes.

{% tabs %}
{% tab title="Outlook" icon="microsoft" %}

1. Open the [Stoïk Report add-in](https://appsource.microsoft.com/product/office/WA200011006) on Microsoft AppSource.
2. Click **Get it now** and follow Microsoft's instructions.
3. Reload Outlook. The **Report Phishing** button appears in the email toolbar.
   {% endtab %}

{% tab title="Gmail" icon="google" %}

1. Open the [Stoïk Report: Phishing extension](https://chromewebstore.google.com/detail/sto%C3%AFk-report-phishing/cpppidkopihnhbbnccpbacacmekcpich) on the Chrome Web Store.
2. Click **Add to Chrome**, then **Add extension**.
3. Reload Gmail. The button appears at the top of every email.
   {% endtab %}
   {% endtabs %}

## Troubleshooting

<details>

<summary>I don't see the button after installing</summary>

Reload Gmail or restart Outlook. In Outlook desktop, the add-in can take a few minutes to sync.

</details>

<details>

<summary>I reported an email by mistake</summary>

No problem. Keep using your inbox as normal. Reporting a legitimate email has no impact on your account.

</details>

<details>

<summary>The button doesn't open the confirmation</summary>

Check that you use the latest version of Chrome (for Gmail) or Outlook. If the issue persists, contact your IT team.

</details>


---

# 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/human-security/report-button/employee-guide.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.