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

# 2026.08.0

Release date: August 5, 2026

This release is about the layer underneath your dashboards. **SharePoint reaches general availability** with full lineage, ownership, and sprawl monitoring; BI360 gains a Data tab that shows where your data actually comes from, how reliably it refreshes, and who is creating it; and the **Datalogz MCP server enters preview**, opening your governance metadata to AI agents.

This release helps your teams to:

* Govern SharePoint content in production the same way they govern BI, with lineage, ownership, and sprawl monitoring included
* See their data sources, refresh reliability, and content creators in one place in BI360
* Query their analytics estate from an AI agent through the MCP server, now in preview

### What's New

#### **SharePoint: now generally available**

[SharePoint](/guides/organizational-setup/connector-onboarding-guide.md) moves out of early access and into general availability. Content is inventoried, monitored, traced, and clickable, on the same footing as your BI connectors.

* **Clickable source URLs** on every inventory asset tab, so you can jump from an asset to the live document
* **Lineage** on the asset side panel, with parentage shown as "Belongs to" so you can see where a document sits in its site and library structure
* **Sprawl monitors** for ownerless content and for stale or empty content, with a dedicated SharePoint tab in the Monitor Catalog
* **Full library crawling**: every document library on a site is now crawled, not just the default "Documents" library

**Result:** SharePoint sprawl gets the same ownership and staleness treatment as the rest of your estate, across all of your content, not a fraction of it.

#### **MCP server: now in preview**

The Datalogz MCP server is available in preview, letting AI agents and assistants query your governance metadata directly.

* Ask about inventory, ownership, lineage, usage, and alerts in natural language from any MCP-compatible client
* Queries run against generated dbt models, so answers stay consistent with what you see in the product

**Result:** Your governance data becomes something your team's AI tooling can reason over, not just something they read in a dashboard.

#### **Bring your own Tableau Connected App**

[Tableau authentication](/guides/organizational-setup/connector-onboarding-guide.md) now supports a user-supplied, pre-created Connected App alongside the existing setup flow.

* Provide your own Connected App credentials during connector setup
* Useful where security policy requires the app to be created and reviewed inside your own tenant

**Result:** Tableau connects on your organization's terms, without a policy exception.

### Enhancements

#### **Clearer alerts**

* Alert stat cards now respect the filters applied to the table beneath them, so the numbers match what you are looking at
* Alert scoping is unified across **View by Alerts** and **View by Assets** and the same filters produce the same population in both views
* Long-refresh monitors only flag a duration when the refresh is still scheduled, removing noise from retired content
* Customer-facing monitor descriptions have been cleaned up for clarity

#### **Platform Stability & Performance**

* Inventory Summary refreshes no longer deadlock. Large environments that previously saw 10+ hour refreshes now complete normally
* MCP now queries through generated dbt models rather than hand-written SQL, making its results consistent with the rest of the platform and simpler to extend

### **Bug Fixes**

* **Spotfire:** asset views now return one row per GUID, unbreaking the inventory grid
* **Spotfire:** source lineage is captured, and all owners are retained rather than only the first
* **Qlik:** the Team and Inventory Summary tab is hidden for Qlik teams, fixing an empty-users redirect
* **SAML SSO:** sign-in now succeeds with identity providers that send empty attributes
* **Sign-in:** plus-addressed email addresses are accepted
* **Similarity:** credential refresh works again after a regression introduced in a prior hotfix


---

# 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.datalogz.io/guides/release-notes/2026.08.0.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.
