---
updatedAt: 2026-02-24T11:33:05.000Z
agentTools:
  projectIndex: https://help.zluri.com/llms.txt
---

# Analytics in the Core Platform

Zluri’s Analytics module gives you the flexibility to build powerful visualizations, track access trends, and monitor security and compliance metrics. It consists of three core components: **Dashboards**, **Widgets**, and **Reports**.

<Image align="center" src="https://files.readme.io/16e127d92bd6fccf1b437cf5e083014273be51956f77043724a3e3e92ae5197b-BI1.webp" />

Analytics in Zluri follows a layered structure:

> **Overview** → built on → **Dashboard** → composed of → **Widgets** → built from → **Dataset + Chart**

# Overview

The **Overview** is the default landing page when accessing Zluri's **IGA** or **SMP** modules. It provides quick, high-level summaries of metrics that matter to you or your organization.

* Can be configured as a **Personal Overview**, **Org Overview**, or fallback to **Zluri Default Overview**
* Powered by dashboards defined at the user or organization level

# Dashboard

A **Dashboard** is a customizable collection of widgets designed to deliver visual insights.

* Can be created, shared, and published
* Usable by individuals or teams
* Supports diverse use cases: Access reviews, offboarding progress, app usage metrics, risk scores, etc.

# Dataset

A **Dataset** is a structured data collection tied to specific entities such as:

* Users
* Applications
* Workflows
* Activities

Each Overview page in Zluri (whether SMP or IGA) is backed by a dashboard, which is composed of widgets. Widgets, in turn, are built using:

* A **Dataset** (source data)
* A **Chart** (visual format)

# Widgets

**Widgets** are the visual building blocks within a dashboard. Each widget shows a specific metric or trend using:

* A **Dataset** to define what data is shown
* A **Chart** to determine how it's displayed

> **Example**:\
> A widget titled *“Users with Unused App Access”* might use a dataset of access logs and display a bar chart with usernames vs. last used date.