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

# Version 1.65

Version 1.65 brings Material's new navigation to everyone, and gives you a rebuilt Email Redaction report. It also brings the suggested classification flow to email threat issues.

***

## :tada: New

### The new navigation is here

In version 1.64 we previewed a new navigation built around the outcomes you care about. It's now live. [Learn more about the new navigation](https://docs.material.security/introducing-materials-updated-navigation.md).

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FAlP7Horpo1sTCqNFRWVz%2Fimage.png?alt=media&amp;token=5cc2d0ab-b23b-49de-827f-1990d9c38325" alt=""><figcaption></figcaption></figure>

***

### A rebuilt Email Redaction report

One new report now replaces the previous [Email Redaction](https://docs.material.security/email-protections/email-redaction.md) and Sensitive Content reports. It shows you where redaction stands today and how it's changing over time.

To view it, from the left navigation expand **Email Redaction**, then click **Report**.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FZ2C8rV4IsHWsTEJDPyQy%2Fimage.png?alt=media&amp;token=1176f54b-a6f8-4d0e-be85-3ea8312e9f3d" alt=""><figcaption></figcaption></figure>

The report includes:

* An estimate of how many messages are currently redacted, with a weekly trend
* Histograms of access requests and of how old the retrieved messages are
* A chart of access requests over time, with the same date ranges as the Email Threats report

The report's weekly history chart appears after Material has gathered a few weeks of data.

{% hint style="info" %}
Email Redaction requires an [Account Takeover Resilience](broken://pages/ybxYchXncDUTCs2GYaEw) (ATOR) license.
{% endhint %}

***

### Set a maximum API token lifetime

You can now limit how long API tokens are active, so no token stays valid longer than your security policy allows.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FyOONIqVABlCdSMCUHrN6%2Fimage.png?alt=media&amp;token=a8ea9765-1771-4bea-ab35-0aec0bda1ce8" alt=""><figcaption></figcaption></figure>

To set the limit, navigate to **Integrations** > **API and MCP**, then click **Settings**.

* A tenant can make the limit shorter than the Global setting, but no longer.
* The token lifetime applies only to newly created API tokens. After you shorten the maximum lifetime and click **Save**, you'll be prompted to choose whether to apply it to all existing tokens, or only to new ones. ![](https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2F1mfWk85UsxwkgB6yAkJT%2Fimage.png?alt=media\&token=55a2af6d-b740-4d4f-91b3-f26cf57ca976)

***

## ✨ Enhancements

### OAuth Security

#### Vendor Trust Level and Scope Risk Level columns

The **OAuth Security** > **Issues** list, including its grouped-by-detection panels, now includes **Vendor Trust Level** and **Scope Risk Level** columns, so you can sort out which apps need attention first. Apps that haven't been investigated show blank values.

For apps synced after these fields were introduced, values appear at sync. For existing apps, they appear after the next scheduled or on-demand audit.

#### A safer default response for OAuth apps

Only apps classified as **Malicious** now default to **Revoke token for all users** and **Notify revoked users**. Suspicious, Overprivileged, and Unnecessary apps default to no automatic response.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FZqWDsQzcmpQNZN8qDfjv%2Fimage.png?alt=media&amp;token=47db6b17-2aa2-4bb7-827e-4a5220501952" alt="" width="375"><figcaption></figcaption></figure>

To review your defaults, navigate to **OAuth Security** > **Settings**, then find **Response by classification**.

{% hint style="warning" %}
Tenants that already saved a value keep it. This only changes the default for settings you haven't saved.
{% endhint %}

***

### Google Drive Security

#### Customize the subject of file remediation emails

You can now override the subject of file remediation emails, using the same variables you already use in the message body. If you don't set a subject, Material keeps using the default.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FUZBsK3nepVaNrMQ0JHya%2Fimage.png?alt=media&amp;token=f2d7e1e8-b4e9-4c41-88d7-24a6930e3dbd" alt="" width="375"><figcaption><p>Detection Detail View > Response > Send email</p></figcaption></figure>

If a subject or message includes a variable Material doesn't recognize, Material now falls back to the default template and still sends the email.

{% hint style="info" %}
Learn more about [configuring default responses](https://docs.material.security/working-with-issues/respond/configure-default-responses.md).
{% endhint %}

#### Filter issues by file response

The **Response** filter on the Issues page now includes the file response options **Email notification**, **Update permissions**, and **Update labels**.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FJ552xxPZfTA0npEjIRUV%2Fimage.png?alt=media&amp;token=09700fa6-ae6d-445a-a674-fbee829f6e4a" alt="" width="248"><figcaption></figcaption></figure>

You can find file issues by the response Material took.

***

### Email threats

#### Accept suggested classifications on email threat issues

Suggested classifications now work on Email Threat issues the way they do for OAuth apps. When Material has a suggestion, it's staged for you as a draft:

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FuKETSFo5x0GxwSk7UYjU%2Fimage.png?alt=media&amp;token=7ad23419-ecfe-49ef-9974-94d7de15c44b" alt="" width="563"><figcaption></figcaption></figure>

* The response is prefilled with the suggested defaults
* The app asks whether to accept the selected classification and apply the response

Click the check mark to accept, or click the X to reject and share feedback. If you pick a different classification, click **Save changes** to keep it or **Discard changes** to bring the suggestion back.

{% hint style="info" %}
Learn more about [response and remediation](https://docs.material.security/email-protections/email-threats/issues/issue-details/response-and-remediation.md).
{% endhint %}

#### Create sensitive category exemptions

Sensitive category exemptions prevent redaction for messages that match an MQL search. You can now create and manage exemptions in Material.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FLmLsPXqcsbRNk77Sft3w%2Fimage.png?alt=media&amp;token=d1b04373-bdc8-4cf5-9622-08e9904f6f78" alt="" width="375"><figcaption></figcaption></figure>

From the left navigation expand **Detections**, click **Sensitive Categories**, then click **Exemptions** > **New Exemption** (or open the action menu with **⌘K**).

{% hint style="warning" %}
A Disabled status that you set on an exemption for a domain or group now takes effect, so messages that exemption covered for that domain or group can now be redacted.

If you previously created exemptions via the API, review them to make sure each status is what you intend.
{% endhint %}

#### Improved message details

* The actual sender is now displayed when a message from a sender with strict DMARC settings is sent via a Google Group
* The **Detected by** row no longer wraps, and long detection names truncate, with the full name in a tooltip

#### Broader built-in email threat coverage

Material's built-in email threat detection now catches more:

* Scam and content-violation lures
* Business email compromise that sends you to a bad link
* VIP impersonation from free email accounts that asks for a phone number
* Fake suspension notices and fake Microsoft bounce-back messages
* Targeted email threats aimed at executives (VIPs)
* Survey-platform abuse

Existing coverage was also tuned to cut down false positives and catch more lures, such as fake calendar invites and fake password reset messages. You'll see fewer issues for legitimate mail.

{% hint style="success" %}
Built-in detection coverage updates roll out continuously, independent of the release cycle.
{% endhint %}

***

### API, admin, and integrations

#### Batch actions tell you their limits

Batch actions now tell you how many items they can act on at once, so you know when a selection is bigger than the limit.

* The **Issues** list and **File Search** act on at most 500 items at a time
* **Accounts** and **Groups** act on at most 100 items at a time
* If you select more, Material clears the extra selection and explains the limit
* In **File Search**, the **Select all search results** link has been removed since it selected results that batch actions couldn't act on

#### Message search and move-to-inbox API improvements

* In Message Search and the v1 API, `message.from.domains` and `message.from.addresses` now match senders written in the `Name <user@example.com>` form
* The move-to-inbox API now returns the same `X-RateLimit-*` headers as message search, and a rejected batch no longer counts against your usage

{% hint style="info" %}
Learn more about the [Material API](https://docs.material.security/reference).
{% endhint %}

### Admin Roles

You can now enroll admins from the Admin Accounts pag&#x65;**.** From the top toolbar, click **Settings** > **Admin Accounts**. Click **Enroll Admin**, choose the account, select one or more roles, then click **Save**.

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2F1p2bbW6yUpQX6cOA1QR0%2Fimage.png?alt=media&amp;token=d7fe4bcb-f1f5-4b62-9049-e8a89a1aa326" alt="" width="375"><figcaption></figcaption></figure>

Only the roles your own role can grant appear in the list.

***

## 🐛 Fixes

<details>

<summary>Detections and responses</summary>

* On shared instances upgraded from Essentials to Advanced, Advanced detections that stayed locked now unlock, so you can use the detections your plan includes.
* File detection response steps now appear in the order you added them.

</details>

<details>

<summary>Email Identity Protection</summary>

* The Target account list in a Force Unlock request now shows only active accounts.
* In Google Workspace, held account emails that arrive through a forwarding relay now reach the employee's mailbox as the protected message, rather than only the relay address.

</details>

<details>

<summary>Email threats and messages</summary>

* Message details no longer show a permission error when you can view the message but don't have permission to read its issue.
* SPF, DKIM, and DMARC results on message details no longer flicker between an email threat issue and the message group's representative message.
* Reject feedback now has a cancel option, so you can back out without sending feedback.

</details>

<details>

<summary>Navigation and search</summary>

* Clearing the Detections search box and pressing enter/return now clears the filter, so the full list comes back.
* Arrow keys in the search window you open with Cmd+K no longer skip rows, so you can reach every result.

</details>

<details>

<summary>OAuth Security</summary>

* The Scope Level filter's Login only option now shows only apps whose current scopes are login-only, on the OAuth apps list and on an app's Accounts tab.
* Investigation sources now open in their own window. Sources and searches sit in separate scrollable boxes, and sources appear only in the full investigation view.
* Slack messages to users whose app access was revoked now follow the Slack setting under End-user notifications in OAuth Security > Settings. The setting is off by default, so if you've never turned it on, users stop receiving these messages.

</details>

<details>

<summary>Settings and integrations</summary>

* Settings with a set of options, such as Email Bomb Protection, now save correctly after you switch from Inherit to Override.
* Super Admins can now send test events to integrations in tenants other than their primary account's tenant.
* Invalid input when you set up an Okta, PagerDuty, or Slack integration or a SAML connection now returns a clear error instead of a generic failure, so you can see what to correct.
* The Slack, Email, and Webhook event configuration forms have layout and usability fixes.
* The spf field in the suspicious message webhook starter no longer carries DKIM data. This only affects Templated Mode instances.

</details>

***

## :books: New and Updated Documentation

**New**

* [Manage Licenses](https://docs.material.security/administration/manage-licenses.md): How licenses work and how to change who gets one.

**Updated**

* Material Security Documentation: Reorganized homepage and navigation to match Material's new navigation.
* [Connect & Sync](https://docs.material.security/getting-started/deployment-guides/your-first-30-days/1-connect-and-sync.md): New subdomains sync automatically.
* [Errors and Troubleshooting](https://docs.material.security/reference/api-v1/errors-and-troubleshooting), [Material MCP Server](https://docs.material.security/reference/material-mcp-server), and the [Messages API reference](https://docs.material.security/reference/api-v1/messages): Rate-limit responses and how to retry.


---

# 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.material.security/whats-new/previous-releases/version-1.65.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.
