> 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.50.md).

# Version 1.50

We have a number of improvements and fixes to enhance your in app experience including auto-resolving issues in one step, a Trusted Entities improved look and behavior, and improved app views.

## :partying\_face: New

### Resolve issues in one step

After you apply remediations, Material now lets you resolve the issue immediately in the same flow. Previously that required a separate manual step — a small friction point that adds up fast when you're working through a campaign.

There are two ways to add this to an issue:

* Add **Resolve issue after applying remediation** to your [default Email Threat responses](/learn-more/risk-areas/email-threats/auto-respond.md#choose-default-responses):

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FnrKVKlRket36BofvYU2k%2Fimage.png?alt=media&#x26;token=045c6042-92a4-488a-b000-c7a9fefd7f08" alt="resolve issue after applying remediation setting location" width="563"><figcaption></figcaption></figure>

* Update the response in an individual issue to include **Resolve issue after applying remediation**. This manually resolves the issue immediately.

***

## ✨ Enhancements

### Trusted Entities Updates

We've made some changes to Trusted Entities to improve the workflow and clarity:

**Location update:**

* Trusted Entities is now located in the workspace, under **Detections** (rather than in settings). It's relevant to how detections behave; it should live where your team is already working.

<figure><img src="/files/kZhC1V5Gfy7f7vjneZRx" alt=""><figcaption></figcaption></figure>

**Trusted Entity details card update:**

* **The descriptions are clearer**. Each setting now explains what it actually does, so there's less guesswork when you're configuring how the detection engine applies trust.

  <figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2F6tlKj66mbBhVAuUFsyLS%2Fimage.png?alt=media&#x26;token=880b5ac1-975a-4780-bfb9-026eb4594df1" alt="trusted entities settings" width="563"><figcaption></figcaption></figure>
* **There's an activity timeline**. You can see who changed which setting and when and leave comments to explain why. No more mystery allow-list entries two years later.

  <figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FikFLRFOZPE4guT0ZPqZm%2Fimage.png?alt=media&#x26;token=695bc280-1bd5-45ed-affe-18786c29a535" alt="trusted entities timeline"><figcaption></figcaption></figure>
* **Trusted entity recommendations are more useful**. We filtered out common public domains (Gmail, GitHub, and the like) from allow-list recommendations. They were cluttering the list without adding value.

**Additional option when ignoring issues:**

* **You can now create safe issues tied to a Trusted Entity**. Previously, matching messages were just dropped. Now you have the option to surface them as safe issues, which gives you a cleaner audit trail without adding noise to your queue.

  <figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FEzi3S0RlvvKIu5uvVpuj%2Fimage.png?alt=media&#x26;token=32ce66ad-1c2a-4afe-b337-06109cff387e" alt="ignored issues choices in trusted entities settings"><figcaption></figcaption></figure>

**API updates**:

* **Bulk management via the API**. If you're managing Trusted Entities at scale, bulk delete and update via the API are now available.

### Apps tab redesign

OAuth apps and Email Verification apps now have their own dedicated views, with scope details surfaced inline, cleaner filtering, and better visual hierarchy throughout. If you've ever had to zoom in to figure out what a connected app actually has access to, this should help.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FcHd6Pj2SqsVobOLQ5xn5%2Fimage.png?alt=media&#x26;token=fa228c9c-4388-4f84-824a-8bab86928a7d" alt="explorer apps view"><figcaption></figcaption></figure>

### Better signal for link-based threats

We've expanded the signals Material captures when evaluating links. This doesn't change what you see in the UI today, but it gives our detection engine more to work with when evaluating malicious links in email and improves determinations.

### Novel sender alerts are smarter about direction

Inbound novel sender checks now only look at your inbound history. Previously, sending an email to someone new could trigger a novel sender flag on the way back in.

***

## 🐛 Fixes

* **Detection enable/disable works reliably again**. The toggle was miscalculating status in some configurations.
* **Message search with `riskType=none` returns correct results**. A bad constraint was breaking this filter.
* **Campaign message counts are accurate**. A calculation error in phishing campaign summaries was producing wrong numbers.
* **The risk-flow chart handles edge cases gracefully**. There's no more blank Sankey chart when there's nothing to display.
* **Domain deletion is clean**. Deleting a domain now properly handles associated email threat issues first, no orphaned data.
* **Compact layout renders correctly**. A rendering issue in the classification and remediation sections in compact view.

## :books: New and Updated Documentation

* Trusted Entities updated
* File search doc updated
* [Message search](https://docs.material.security/getting-started/fundamentals/explore/message-search#h-faq) updated (search time frame)


---

# 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.50.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.
