# Understand Sanas Reports

- Updated on Jul 31, 2025
- Published on Oct 23, 2024

- 2 minute(s) read

### Introduction

The **Report** page serves as your centralized analytics console for monitoring and analyzing Sanas app usage across teams within a Workspace. It consolidates key metrics to help you gain insights and make data-driven decisions.

---

### Report summary

The report summary is the header of your Report page, highlighting the following key metrics:

| Metric | Description |
| **New users** | New app users created within the selected Workspace during the selected period. |
| **Active users** | - App users that activated the Sanas app in the selected period.<br> - **Example**: The app user launches and activates the Sanas app on their computer (need not to engage the microphone or make a call). |
| **Sanas disabled** | - App users with Sanas toggled off on their app.<br> - Click **Sanas Disabled** to review the metric for individual app user.<br> - **Example**: App user launches and activates the Sanas app, then manually it turns off. |
| **Incompatible setups** | - App users encountered system compatibility errors during the selected period.<br> - Click **Incompatible setups** to review the metric for individual app user.<br> - **Example**: Incompatibility error occurs when user disconnects their headset during an active session. |

---

### Utilization table

The Analytics table offers a detailed overview of each individual app user within the selected team (default: All teams) for the specified time period (default: Today). It includes the following metrics:

.png?sv=2026-02-06&spr=https&st=2026-07-18T06%3A53%3A00Z&se=2026-07-18T07%3A05%3A00Z&sr=c&sp=r&sig=3EC2NiRpFXbb2e4V2b8t3zoGOaMVubUa%2BalJm8CQp74%3D)

| Metric | Description |
| **User ID** | Unique identifier |
| **Name** | Full name |
| **Team** | Currently assigned team |
| **Machine** | Computer unique identifier |
| **Login** | - Timestamp of the first Sanas app interaction. <br> - **Example**: User logged in to the Sanas app at the beginning of their work shift. |
| **Last seen** | - Timestamp of the last Sanas app activity. <br> - **Example**: A user logs out, or an inactivity period is detected. |
| **Session** | - The total active time between the Login and Last seen is calculated as the Session duration.<br> - The Session duration excludes any inactivity period longer than 3 hours.<br> - **Example**: If a user logs in at 10:00 AM, becomes inactive from 11:00 AM to 3:00 PM, and resumes activity, the **4-hour inactivity period will be excluded** from the session duration. |
| **App enabled** | - The total time users have the Sanas app activated with the Sanas toggle turned on.<br> - Periods of inactivity—such as app logout, screen lock, or device sleep—are excluded from the total duration. |
| **Status** | - A user's engagement status is displayed as either **Engaged** or **Not Engaged** based on their usage during a selected session.<br> - **Engaged**: The Sanas app was activated and used in at least one call during the selected session.<br> - **Not Engaged**: The Sanas app was activated but not used in any calls during the selected session.<br>- **Usage Consolidation**: If a user accesses the app from multiple devices within the same day (12:00 AM to 11:59 PM), their total usage duration is automatically **consolidated into a single daily entry**. This ensures accurate reporting per user per day, regardless of the number of devices used. |

---

### Important considerations

Please consider the following scenarios to understand the data reporting:

| Scenario | Description |
| **Timezone differences** | - The data displayed is based on the timezone of the admin user viewing the report.<br> - If two admins in different timezones view the same Workspace data for the same date range, slight variations may occur due to differences in their local time settings. |
| **Daily activity tracking** | - App usage data is captured on a daily basis (from 12:00 AM to 11:59 PM).<br> - A new entry is generated each day, aligned with this time window. |
| **Logins on multiple devices** | - If a Sanas app user activates and uses their app through multiple devices in a single day (from 12:00 AM to 11:59 PM), all the detected unique instances (machine + user credentials) of app usage get consolidated into a single line item on the Sanas Report. |

---

### Customize reports

You can tailor your reports using the following filters:

#### **Time Period**

Select a time range to view data for:

- Today ( **default**)
- Yesterday
- Last 7 days
- Last 30 days

#### **Teams**

Choose specific teams in your Workspace to filter the report. By default, **all teams** are included.
