> 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/common-questions.md).

# Common questions

<details>

<summary>What happens if an employee reports a legitimate email by mistake?</summary>

Nothing critical. The report appears in your Reported Threats table with `Pending` validity, or `False positive` if Email Security analyzes it and confirms it is safe. Encouraging employees to over-report is safer than encouraging them to under-report.

</details>

<details>

<summary>Can I see how many reports each employee has submitted?</summary>

Yes. Filter the Reported Threats table by **Reporter** to see all reports from a specific employee.

</details>

<details>

<summary>Can I respond to the employee who reported the email?</summary>

Yes. Enable **Notify employees of the verdict** so the reporter automatically receives an email with your verdict. See [Notifying the reporter](https://docs.stoik.io/human-security/report-button/reports.md#notifying-the-reporter). Thanking employees through your own internal channels (email, Slack) also reinforces the behavior.

</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/common-questions.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.
