# Overview Dashboard

### Overview

The **Overview Dashboard**—also called **Engagement & Usage**—gives admins and decision-makers a complete picture of how employees are engaging with MangoApps. It consolidates metrics around users, adoption, collaboration, efficiency, learning, and culture so you can measure impact and optimize usage.

***

### User Highlights

This section provides a snapshot of who is on the platform and how reachable they are.

<figure><img src="/files/qe67STPi36FQ6PPhowH5" alt=""><figcaption></figcaption></figure>

**Total Network Users**: Active network accounts (excluding guests, system, deactivated, or deleted).

**Reachability & Login**: Breaks users into those who have logged in, those never logged in but still reachable (via email/SMS), and those unreachable (missing or invalid contact info).

**Guest Users**: Count of active guest accounts (excludes network/system/deactivated/deleted).

{% hint style="info" %}

### What is a System Account?

A **system account** in MangoApps is a **non-human user profile** created and used by the platform itself to perform automated or background tasks. These accounts are not tied to a real person and are generally invisible to end users.

Examples include:

* Accounts that **send automated notifications** or emails on behalf of the system.
* **Background processes** that log activity or handle integrations.
* Special service accounts provisioned internally for **technical operations**.

***

#### Why Are They Excluded from Analytics?

Since system accounts do not represent actual people engaging with content, they are **excluded from all user-related analytics**:

* Not counted in **Total Network Users** or **Guest Users**.
* Not included in **Adoption scores**, **login sessions**, or **collaboration metrics**.
* Ensures reports reflect only genuine employee and guest engagement.
  {% endhint %}

***

### Time Filters and Data Refresh

The Overview Dashboard supports flexible **time frame filters** so you can analyze trends over the period that matters most. Options include **Last 1 week, Last 4 weeks, Last 12 weeks, Last 12 months**, or a **custom date range** (minimum 7 days, maximum 365 days). When you change the time frame, all graphs and metrics refresh automatically to show data only from that period.&#x20;

A **“Last Updated” timestamp** also appears at the top of the dashboard, indicating when analytics were most recently refreshed (typically within the last 30 minutes).

{% hint style="warning" %}
Time filters do **not** apply to the **User Highlights** section described above.
{% endhint %}

***

### User Lifecycle Metrics

This section tracks adoption and changes in your user base over time.

<figure><img src="/files/mXh9mCHHMSTrvby4vFRg" alt="" width="563"><figcaption></figcaption></figure>

**Network User Adoption Score**: Percentage of network users who engaged with content (view, react, comment, post) in the selected period.

**Adoption Trend**: Line graph of active users over time, showing engagement progress.

**Users Added**: Total new network users created in the domain.

**Guest Users Added**: New guest accounts created.

**User Deactivations**: Total users deactivated during the period.

***

### Platform Utilization & Efficiency

Here you see how effectively employees are accessing and using MangoApps across devices.

<figure><img src="/files/GiQcDvtYhRlTAV0XyUOl" alt="" width="563"><figcaption></figcaption></figure>

**All Login Sessions**: Logins grouped by platform (web, iOS, Android, messenger, desktop).

{% hint style="info" %}
**Counting logic**:

* Each **distinct session** is counted, regardless of the device or platform.
* A single user can contribute multiple sessions (e.g., logging in from web, then iPhone, then Android counts as 3).
* Auto-expired sessions (due to inactivity) are still counted if they were initially established.
* Browser versions are ignored — sessions are grouped by platform (Web, iOS, Android, Desktop, Messenger).
* **Not unique**: This means the metric represents **total session activity volume**, not unique users.
  {% endhint %}

**App Downloads**: First-time app logins after installation on iOS or Android. Here, each user can only appear once (their very first login on iOS or Android).

**Look-Ahead Searches**: Predictive searches where users clicked a result.

**Deep Searches**: Full-content searches performed.

**SMS/Text Sent**: Number of texts sent through MangoApps.

**Reports Generated**: Admin or scheduled reports created.

***

### Collaboration & Knowledge Sharing

This section highlights the content being created and how people are engaging with it.

<figure><img src="/files/vqFuuhQFfk1vANkXzcz5" alt=""><figcaption></figcaption></figure>

**New Content**: Posts, updates, pages, wikis, and files created.

**New Files**: Uploaded documents, images, and videos.

**New Content Count**: Total new items published.

**New Content Contributors**: Unique users publishing or uploading.

**Total Reactions Count**: Number of likes/reactions given.

**Total Comments Count**: Number of comments and replies posted.

***

### Automation & Process Efficiency

This section measures activity in workflows, trackers, forms, and tasks to show process automation.

<figure><img src="/files/6l727d5F405jS58QDnH6" alt="" width="563"><figcaption></figcaption></figure>

**Workflow Actions Triggered**: Total actions executed by workflows.

**Active Workflows**: Workflows that ran at least one action.

**Entries Added**: New entries across all trackers.

**Active Trackers**: Trackers with new or updated entries.

**Submissions Received**: Total form submissions.

**Active Forms**: Forms that received at least one submission.

**Tasks Completed / Created**: Tasks finished or added across teams.

{% hint style="info" %}
Both **Active Workflows** and **Active Forms** metrics are **unique counts** of items that had at least one action/submission, not a total volume count.
{% endhint %}

***

### Learning & Development

This section shows how employees are engaging with learning opportunities.

<figure><img src="/files/UXWyWK4Dst3f0LBLvKkt" alt=""><figcaption></figcaption></figure>

**Active Courses**: Courses with user activity (enrolled, in-progress, or completed).

**Course Assignments**: Number of assigned courses in the selected period.

**Training Time Spent**: Total hours spent completing courses.

**Course Completions**: Total courses finished.

**Learner Progress**: Breakdown of learners by Not Started, In Progress, and Completed.

{% hint style="info" %}
**Counting logic**:

* **Unique stats**: Active Courses and Learner Progress.
* **Total counts**: Course Assignments, Training Time Spent, Course Completions.
  {% endhint %}

***

### Culture Impact

This section captures recognition and feedback activities that shape organizational culture.

<figure><img src="/files/pimcWrSu9BRKo1sBsupi" alt="" width="563"><figcaption></figcaption></figure>

**Recognition Points Distributed**: Total Reward points given during the selected period.

**Recognitions Given**: Total count of recognitions awarded. This count is **not** unique.

**Surveys Created**: New surveys launched.

**Survey Invites Sent Out**: Users who received survey invitations.

**Survey Completions**: Users who submitted completed surveys.

***

### Messaging & Communication

These insights allow administrators to monitor adoption, track engagement trends, and measure the volume of interactions across both Chats and Private Messages.

<figure><img src="/files/yvnYzxdwOhHwD3GFxCda" alt="" width="563"><figcaption></figcaption></figure>

**Chat Analytics**

The Chats analytics suite tracks the velocity of real-time communication across one-to-one, ad-hoc, and team-based conversations.

* **Key Performance Metrics**: Admins can view the Total Chat Messages, Active Chat Conversations, and the number of Active Chat Users. A conversation is considered "active" if at least one message is sent within the selected timeframe.
* **User Engagement**: The active user count focuses on unique, human interactions by excluding system-generated users.
* **Trend Visualization**: A weekly bar chart, Chat Messages Over Time, allows admins to identify peaks in communication and long-term usage patterns. In these counts, each individual message and reply is recorded as a single unit.

**Private Message Analytics**

The Private Messages section provides a detailed look at more formal or directed communications, including single-recipient, multi-recipient, and system-generated notifications.

* **Activity Tracking**: Metrics cover Total Private Messages, Active Conversations, and Active Users within a specific date range. Even if a conversation thread was initiated in the past, it is captured in current analytics if a new message or reply is sent during the selected period.
* **System vs. User Data**: While the total message count includes automated system notifications, the Active Private Message Users metric specifically tracks unique human participants to provide an accurate representation of employee engagement.
* **Longitudinal Data**: The Private Messages Over Time chart organizes data into weekly buckets, making it easy for administrators to evaluate the impact of company-wide announcements or automated system workflows on overall messaging volume.

{% hint style="info" %}
Both sub-sections are designed to provide a consistent view of organizational health. All-time values are available alongside time-specific filters, ensuring that administrators can conduct both immediate pulse checks and long-term compliance audits.

* **Deleted User Retention**: To maintain historical accuracy, interactions from deleted users remain part of the aggregated message totals and trend charts.
* **Flexible Filtering**: Admins can adjust the time range to focus on specific initiatives or quarters, with charts automatically scaling to provide the most relevant data visualization
  {% endhint %}


---

# Agent Instructions: 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:

```
GET https://guides.mangoapps.com/admin-guide/analytics/overview-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
