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

# Version 1.39

## :tools: Enhancements

### 🕵️ Audit Log Improvements

The Audit Log now gives you more visibility into activity, with stronger security coverage, and a smoother layout for compliance teams. Highlights include:

* **Clearer audit log event descriptions**: User-friendly audit messages that explain exactly what happened
* **Better filtering**: More logical category groupings make finding events easier
* **Enhanced details**: Richer context for configuration changes with before/after comparisons
* **Consistent formatting**: Standardized audit log structure across all event types
* **Better logging coverage**: Architectural improvements that ensure comprehensive audit logging
* **Improved category structure**
  * **Reduced complexity**: Consolidated from [18 to 11 intuitive, noun-based categories](/administration/audit-log/audit-log-updates-version-1.39.md)
  * **Better organization and naming**: Categories now align with how your teams think about security events

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FXn9i9YuHnH133BtUPXz7%2Fimage.png?alt=media&amp;token=bd6a5f0e-2192-4992-96f5-8047ce8b0f3b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
You likely need to make a few updates to your existing event subscriptions to take advantage of these improvements (and prevent event subscription interruptions).

:bulb: [Learn more about the improvements and how to update for them here](/administration/audit-log/audit-log-updates-version-1.39.md).
{% endhint %}

***

### 📈Most Targeted Users Gallery

<figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2FfyrwFeB7jemFxxmEdRI1%2Fimage.png?alt=media&amp;token=eaf6d5ff-2442-47ef-9d76-c1b13d6246d6" alt=""><figcaption></figcaption></figure>

Identify which individuals or groups are receiving the highest volume of phishing attempts. This helps you direct awareness training and simulations where they’ll have the most impact. Think of it as your security wish list, but instead of yachts and Oscars, you’re prioritizing resilience.

To view: from the left navigation expand **Reports**, then click **Email Threats**.

***

### 🔍 Message Search

Autocomplete now includes your past searches, making it faster to repeat common queries.

***

## 🐛Bug Fixes

* **API Reporter Updates**: When a phishing case status is updated via API, all previous reporters now reliably receive the latest set of acknowledgements.


---

# 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/1.15-to-1.43/version-1.39.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.
