> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/learn-more/risk-areas/email-threats/reports.md).
# Email Threats Reports
There are [metrics](/learn-more/risk-areas/email-threats/investigate/issue-details.md#metrics) available in the issue view details related to individual issues. To see reports containing data across issues, trends, etc.:
From the left navigation, expand **Reports** then click a **report name**.
## Issues Created, Affected Accounts, and Message Counts
In reports, you may see issues created and affected accounts. These do not represent the total number of messages. Instead,
* A issue represents a group of similar messages that Material has determined represent a campaign.
* An Affected Account is a mailbox that has at least one suspicious message. Some accounts might have received many malicious messages.
Issues are a helpful way of understand the breadth of email-based threats facing your organization. Affected Accounts help you understand the scope of those attacks across your organization.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.material.security/learn-more/risk-areas/email-threats/reports.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.