> 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/bi-360/bi-360-insights.md). # BI 360 Insights **BI 360 Insights** breaks your analytics estate down by layer: an Overview, plus dedicated tabs for the organizational layer (workspaces, projects, streams), the reporting layer (reports, dashboards, apps, workbooks), and the data layer (semantic models, datasets, data sources, dataflows). BI 360 Insights also include department-level breakdowns for organizations that have connected Entra ID. Department insights answer the question: which teams are driving usage, owning content, and consuming licenses, and which are not? Where Entra ID is connected, every relevant insight can be sliced by department. ### Overview tab The Overview tab is the primary health dashboard: a fast, cross-tool snapshot via KPI cards and the BI Health chart. **KPI summary cards.** Four cards summarize the state of your BI environment, each broken down by BI tool: * **Data**: total data assets (semantic models, data sources, data connections, dataflows) * **Reporting**: total reporting assets (reports, dashboards, workbooks, apps) * **Organizational**: total organizational units (workspaces, projects, streams) * **User**: total users registered across connected tools **BI Health chart.** A Sankey flow maps asset categories (Reporting, Data, Organizational, User) to their health status (healthy or unhealthy) and the BI tool they belong to. Use it to spot which platform or asset category carries the highest share of unhealthy assets. ### Organizational tab Tracks the health of your BI hierarchy and user engagement within it: workspaces (Power BI), projects (Tableau), streams (Qlik Sense), and workbooks or folders (Sigma). **KPI cards:** * **Active Folders**: folders with recent activity as a share of all folders * **Inactive Folders**: folders with no recent activity, candidates for cleanup * **Active Users**: users who accessed BI content recently out of total users * **Inactive Users**: users with no recent BI activity, potential unused licenses **Analysis.** The left panel shows summary metrics; the Activity Trends chart plots folder activity over the last 30 days by tool. Key metrics: Activity Trends (% change vs. last 30 days), Total Top Level Folders, Folder Growth Rate, Folder Content Growth Rate, Adoption Rate (of the people you are paying for, how many actually get value), and User Engagement Score, which moves beyond "did they log in?" to "how deeply are they engaging?", distinguishing power users from passive consumers. {% hint style="info" %} High inactive user counts are a strong signal for license optimization. Cross-reference with your BI tool's license data to identify recovery opportunities. {% endhint %} **Department insights** (requires Entra ID): a sortable Department User Breakdown table with user counts and activity per department, and License Utilization by Department, color-coded by utilization band (red below 30%, amber 30 to 70%, green above 70%). ### Reporting tab Focuses on the health and engagement of reports, dashboards, and other content assets. **KPI cards:** * **Active Assets**: reporting assets with recent viewer activity out of all assets * **Active Reports**: reports accessed recently out of total reports * **Active Dashboards**: dashboards accessed recently out of total dashboards * **Unique Report Viewers**: distinct users who viewed any report during the period **Analysis.** The Viewer Trends chart plots unique daily viewers over time by tool. Key metrics: Viewer Trends (% change vs. last 30 days), Total Reports, and Reports Growth Rate. {% hint style="info" %} A low Active Assets percentage alongside a high Total Reports count is a strong indicator of report sprawl. Use Global Inventory to investigate and identify stale content. {% endhint %} **Department insights** (requires Entra ID): Department Dashboard Ownership surfaces which departments own which dashboards and reports, and whether those assets are actively used, so cleanup work can be routed to the right team. ### Data tab Provides visibility into the health and reliability of your underlying data layer: semantic models, data connections, dataflows, and scheduled refreshes. **KPI cards:** * **Successful Refreshes**: refreshes that completed without error as a share of all refreshes * **Failed Refreshes**: refreshes that failed and need investigation to prevent stale reports * **Active Data Assets**: data assets in active use out of all registered data assets * **New Data Assets**: data assets added recently as a share of all assets **Analysis.** The Viewer Trends chart plots data asset usage over time. Key metrics: Viewer Trends (% change vs. last 30 days), Total Refreshes, Scheduled Refreshes, and Data Assets Growth Rate. {% hint style="info" %} Failed refresh rates directly impact report reliability. If Failed Refreshes is above 0%, investigate the affected assets in Global Inventory before escalating to your BI tool administrator. {% 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/bi-360/bi-360-insights.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.