> 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/oct-2025.md). # Oct 2025 **Data Access Policy Enhancements** * **Power BI Governance** – Rolled out "Delegation Admin" capabilities for granular administrative control. This includes policy administration by workspace. * **Access Governance Object Sync** – On-Demand sync services and APIs for common sync services to streamline policy enforcement. * **Entitlement Expansion** – Entitlement data APIs to fetch roles and privileges based on database/schema/object access. * **Attribute Migration Feature** – Download of migration scripts directly from the console and performing attribute migration from one environment to another. **Data Security Posture Management Enhancements** * **Activity Reporting** – Enhanced User Activity Reports with advanced filtering capabilities and a new option to generate reports directly from the access policies page. * **Monitoring Policies** – Addition of new policies to detect for "User Enumeration" attacks and detection of table tagged as sensitive in the backed up table list. --- # 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.trustlogix.io/release-notes/2025-q4-releases/oct-2025.md?ask=&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.