> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/release-notes/2025-q4-releases/nov-2025.md).

# Nov 2025

**Data Access Policy Enhancements**

* **Agent Access Governance** – TrustAI feature in preview to implement AI Agent-specific resource access policies to control the data access for end users via AI Agents.
* **Application Access Governance** – TrustApp feature in preview to try out resource-specific access management by applications.
* **MCP Service** – TrustLogix MCP server preview for consumption with OAuth based authentication.

**Data Security Posture Management Enhancements**

* **Activity Reporting** – Entitlement Report fixes to handle multiple user selections across databases, schemas etc.
* **Monitoring Policies** – Addition of “Mute policy” feature to the monitoring policies across all the data sources which will pause the execution of a certain monitoring policy.
* **Monitoring Policies** – Improved data monitoring policy UI layout to maintain consistency with the access governance UI.


---

# 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.trustlogix.io/release-notes/2025-q4-releases/nov-2025.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.