> 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/1.15-to-1.43/version-1.31.md). # Version 1.31 ## ✨ New ### Okta SSF Integration We’ve integrated with Okta’s Shared Signals Framework (SSF) to provide security event notifications within Okta environments. This enhances incident detection, response, and automation, ensuring that security-relevant events from Material (such as Issue changes) are seamlessly transmitted to Okta. Learn how to integrate with [Okta SSF](/integrations/integration-fundamentals/identity-integrations/okta-ssf.md).

*** ### Quick Actions in Message Details Digging into a message just got smoother. We’ve added a dialog in **Message Details** so that you can quickly jump straight to message search, add a trusted sender, or block a sender. Fewer clicks, more control. {% @arcade/embed url="" flowId="OZwYr6AzMATXkxdbDtT7" %}

Create a Trusted Entity from an Issue

1. Begin in a specific issue. 2. In the message details, click the **Sender Address**.

4. From the quick action menu, click **Trust**. 5. Choose to apply this to one tenant or globally, subdomain inclusion, and phishing and file settings: 6. Click **Save**.

To reverse this action, click **Un-trust** from the same quick action menu in the issue.

Block a sender from an Issue

You can block a sender directly from the message details in an issue to prevent them or their associated domain from delivering messages into inboxes. 1. Begin in a specific issue. 2. In the message details, click the **Sender Address**. 3. From the quick action menu, click **Block**.

4. Choose to block just this sender's email address, or their entire domain:

Block one sender or any sender in their domain

5. A custom detection is created deleting messages from that sender. Click the pop-up in the bottom left corner to view the detection (or from Detections, search for the domain to find the detection).

To unblock a sender, archive the detection. {% hint style="warning" %} It's possible to both Trust and Block a sender from the quick actions menu. If both actions are taken, we defer to the Trusted Entity and the sender is **not blocked,** regardless of existing or future detections. {% endhint %}

Open message search from message details

1. Begin in a specific issue. 2. In the message details, click the **Sender Address**. 3. From the quick action menu, click **Search messages.**

5. The message explorer opens pre-populated with a query searching for all messages from this sender.

*** ## 🛠️ Updates & Bug Fixes * **Event Subscription UI polish** - Cleaner, more intuitive, and easier on the eyes. * **Table Columns, Remembered** - Column reordering in tables now sticks around, even after a page reload. Your layout, your rules. * **Smarter Message Search Links** - Clicking into a message search now pre-fills the form with context. Less typing, more finding. * **Issue Search Upgrades** - You can now filter issues by classification and assignee. Because precision is powerful.

*** ## 🛡️Email Threat Detection Tuning * Enhanced detections that depend on sender reputation to include more robust context for advanced tactics. * Added improved brand impersonation detections including specific coverage for several high profile brand targets. * Added new high fidelity detections in response to specific observed campaigns and techniques. --- # 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/1.15-to-1.43/version-1.31.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.