> 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/2.13-2026.06.0.md). # 2.13 (2026.06.0) Release date: June 17, 2026 This release puts more control in the hands of the people who run analytics. Inventory becomes personal and shareable with Custom Views, Shared Views, and Favorites. Alerts get sharper with 30/60/90 day timeframes and an asset-centric view. The Databricks connector arrives in preview, and immediately includes lineage. This release helps your teams to: * Work from their own saved slices of the analytics estate, and share them * Separate genuinely stale assets from recently active ones before acting * See risk rolled up by asset, not buried in a flat alert list ### What's New #### **Custom Views** Inventory now lets each user save and switch between their own views of the analytics estate. * A view picker with **Edit Columns**: reorder, rename, freeze, and add or remove columns * Save, switch, duplicate, rename, set a default, and delete views * Shareable links that survive navigation * Built-in system views: All Assets and Unhealthy **Result:** Every team works from the slice of the estate that matters to them, without rebuilding it on each visit. #### **Shared Views** Custom Views can now be shared with a team. * Save a view as personal or shared with your team * Owner-or-admin management of shared views, with the ability to change visibility after creation **Result:** A team converges on one agreed view of the assets they own. #### **Inventory Favorites** Star the assets you care about and return to them fast. * A star column on the Assets grid and a My Favorites system view * Favorites work across Power BI, Tableau, Sigma, Qlik, Databricks, and SharePoint **Result:** Quick access to the handful of assets each owner watches most closely. #### **Self-service SSO and passwordless sign-in** Administrators can now configure single sign-on without a support ticket. * A self-service SAML SSO configuration screen, gated to the Sys Admin permission * Passwordless email login code flow * A config-driven announcement banner on the login screen * An accessibility overhaul and split-screen redesign of the sign-in experience **Result:** Faster, more secure onboarding that an administrator controls directly. #### **Alerts: 30/60/90 day timeframes** Alerts and their underlying monitors can now be viewed across a window you choose. * Multi-window monitors run 30, 60, and 90 day timeframes for the Power BI stale and unused family: unused datasets, unused reports, orphaned reports, and high-refresh and Snowflake refresh datasets * A timeframe filter on the alerts list and drill-down tables, with 30/60/90 badges on alert rows and beside the Summary title **Result:** Owners separate genuinely stale assets from recently active ones instead of chasing a single fixed window. #### **Alerts: Group-by-assets view** Roll alerts up by the asset they belong to. * A View by asset grouping with a server-side grid, category badges, and drill-down to the underlying alerts * Type and Owner column filters on the grouped view * Each monitor now carries a category, derived from its health tags and surfaced as a badge **Result:** Instead of a flat alert list, owners see which assets carry the most risk and act on the asset, not the individual alert. #### **Databricks connector with lineage and monitors (Preview)** Databricks is now in preview. The connector includes: * A Lineage tab for Databricks asset types * Databricks Monitors that can be enabled in the Monitor Catalog **Result:** Upstream and downstream visibility for Databricks assets, with monitoring. ### Enhancements #### Sigma monitors and BI 360 Sigma becomes a first-class connector for monitoring and executive reporting, building on the Sigma connector and lineage shipped earlier. * Predefined Sigma monitors with RBAC, plus a Sigma tab in the Monitor Catalog * Sigma included in BI 360 reporting and owners-per-platform, the scheduled-refresh heatmap, and monitor status * Workbook pages metrics and report-owner attribution for Sigma **Result:** Sigma content is monitored and costed alongside every other tool. #### Tableau enhancements A broad set of Tableau improvements. * A Created Between date filter on the cluster map * Embedded datasources captured and surfaced, plus a Published vs Embedded datasources chart on the Data tab * Tableau content engagement on the Executive Summary and BI360 engagement metrics * Similar Assets for Tableau dashboards and datasources * Department asset-mapping inheritance with site, project, workbook, and view precedence **Result:** Tableau reaches parity on engagement, similarity, and ownership analytics. #### Alert workflow comments * Add a comment when you change an alert's workflow status * The latest comment shows on the alert Details tab * Comments persist in all cases and status labels are normalized **Result:** An audit trail of who changed what and why, attached to the alert. #### Auto-close stale alerts * EVENT alerts with no recent activity auto-close as Potentially Resolved after 30 days * The event-occurrence chart window extends past the last-seen date for open alerts so the trend stays accurate **Result:** The alert queue reflects reality, and owners focus on what is still live. #### BI360 ownership analytics Building on department health, BI360 adds new ways to see who owns what. * A Reports by Department chart with a Hide Unattributed toggle * A Unique Owners metric and a Department Assets vs Unique Owners chart * Deleted user attribution for assets whose owner no longer exists **Result:** Clear accountability for analytics by department, including the gaps. #### Asset comparison and detail * Semantic Model and Data Sources rows added to the Compare Similar Assets modal * Full table columns shown in the asset detail panel * Workbook pages information in the inventory workbook details panel **Result:** Richer side-by-side comparison and deeper single-asset detail. #### SharePoint connector (Preview) SharePoint content enters the inventory. * Sites, Drives, Files, and Workbooks inventory tabs * Workbook side-panel detail tabs for charts, pivots, and comments **Result:** SharePoint-hosted analytics stop being a blind spot in the estate. #### Smaller enhancements * **BI Similarity sliders clarified:** renamed to Top views and Top nodes, scoped to reports, and ranked by 30-day views * **Duplicate formula monitor:** a new predefined monitor that flags duplicate formulas, excluding trivial expressions and shared-data-model cases * **Viewers CSV export** lists Email first and mirrors the active view * **Grid polish:** clearer custom scrollbar, tighter row height, and sticky Edit Columns headers ### Platform Stability & Performance * The Top N% by views slider on the BI Similarity cluster map now filters server-side, for both correctness and speed. ### Bug Fixes * Corrected an adoption aggregation that could produce over-100% rates; Power BI adoption now falls back gracefully when AAD is not connected. * Power BI personal workspaces are now excluded from organizational folder metrics. {% hint style="info" %} New to saved views? See [Search and Filters](/guides/inventory/search-views-and-filters.md) to get the most out of Custom Views, Shared Views, and Favorites. {% endhint %} --- # 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/2.13-2026.06.0.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.