> 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/whats-new/previous-releases/version-1.53.md).

# Version 1.53

Version 1.53 adds a message activity timeline, AI model attribution, and broader CSV exports to deepen investigation context. It also improves issue counts, attachment context, trusted sender visibility, and tenant-aware detection filtering.

***

## :partying\_face: New

### Message activity timeline

**Message details** now include a full event timeline for each message. It displays detections, issue assignment, remediation, redaction, and analyst comments in one scrollable view.

Use the timeline to trace a message from first detection to final action without switching views. When the message belongs to an issue, related issue context also appears.

This builds on the issue-level timeline introduced in [Version 1.52](/whats-new/previous-releases/version-1.52.md). For more investigation context, see [Issue Details](/learn-more/risk-areas/email-threats/investigate/issue-details.md).

<figure><img src="/files/kCKiifRFDdVaValQxVBR" alt=""><figcaption><p>Message details now show the full history for a message in one view.</p></figcaption></figure>

### AI model attribution in message analysis

When Material AI flags a message, the analysis card now shows the model name and version that produced the result.

This makes AI-driven detections easier to audit, compare, and report on.

[Learn more about Material message analysis here](/getting-started/fundamentals/investigate/evidence/message-analysis.md).

<figure><img src="/files/5zWSjhPJDlpjwqVj85yT" alt="Version 1.53 message analysis card showing the AI model name and version for a Material AI result."><figcaption><p>Message analysis now shows the AI model name and version.</p></figcaption></figure>

***

## ✨ Enhancements

### CSV exports across Explorer

New CSV export options make ad hoc analysis easier:

* **Accounts** and **Groups** now support CSV export.
* Each export supports up to 20,000 rows.
* Exports respect active filters.

With this change, every [**Explorer**](/getting-started/fundamentals/explore.md) view now supports CSV export. The **Issues** CSV also adds four columns:

* `Issue ID`
* `Assignee`
* `Ignore reason`
* `Resolve reason`

<figure><img src="/files/NlZzQsAa8vc5LW6VOaVf" alt="version 1.53 CSV export options for Explorer views and Issues export fields."><figcaption><p>CSV exports now cover all Explorer views</p></figcaption></figure>

### Issue count in the issues table

In the ungrouped **Issues** view, the header now shows the total number of issues that match your current filters. The count stays visible while more results load, so you always know how many issues you're looking at before you start triaging.

<figure><img src="/files/JMlGHqSBe33o2XxE856d" alt=""><figcaption><p>The issues count stays visible while more results load.</p></figcaption></figure>

### MIME type column in message attachments

The message attachments view now shows MIME type. Analysts can confirm a file's actual type without opening or downloading it.

<figure><img src="/files/UZBYUb0Nqth9Q9KelRG1" alt=""><figcaption><p>MIME type helps confirm an attachment's actual file type.</p></figcaption></figure>

### Trusted Entity badge in sender reputation

When a message sender matches a configured trusted entity, the sender reputation section now shows a **Trusted Entity** badge with a direct link to [Trusted Entities](/getting-started/fundamentals/detect/trusted-entities.md).

This makes manual trust decisions easier to spot during investigation.

<figure><img src="/files/wQeTjlfsre3SfIEHuoY3" alt="Version 1.53 sender reputation section showing a Trusted Entity badge and link for a matched sender."><figcaption><p>Sender reputation now highlights trusted entities.</p></figcaption></figure>

### Filter detections by tenant type

The **Detections** list now filters by the selected tenant's email provider:

* **Google Workspace** hides Microsoft 365-only detections.
* **Microsoft 365** hides Google Workspace-only detections.
* **Global** shows all detections.

System-agnostic detections, such as Okta, always appear.

***

## 🐛 Fixes

* **Messages no longer attach to cleared issues:** Incoming email threat messages were sometimes assigned to issues that were already cleared or closed. Messages now land in the appropriate open issue.
* **Assignee lists now load completely:** The **Assign to...** menu on issue details and bulk assignment now loads the full list of assignable accounts with pagination. Analysts in larger organizations can now find the right assignee.
* **Duplicate trusted entity API errors now return 409:** Creating an existing trusted entity through the API now returns `409 Conflict` instead of `500 Internal Server Error`.

***

## 🗑️ Removed

* **Known Breaches**: We removed the Known Breaches feature. It previously checked addresses against the HaveIBeenPwned (HIBP) breach database.

***

## :books: New and Updated Documentation

* [Integrations Guides](/integrations/integration-fundamentals.md)
* [Message Analysis](/getting-started/fundamentals/investigate/evidence/message-analysis.md)


---

# 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/whats-new/previous-releases/version-1.53.md?ask=<question>&goal=<endgoal>
```

`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.