--- title: "Understand Sanas Reports" slug: "sanas-reports" updated: 2025-07-31T08:38:04Z published: 2025-07-31T08:38:04Z canonical: "help.sanas.ai/sanas-reports" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.sanas.ai/llms.txt > Use this file to discover all available pages before exploring further. # Understand Sanas Reports ### 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: ![](https://cdn.document360.io/9bc36e9c-f402-4213-b56f-4ecdf805bb1a/Images/Documentation/image-1746194870743.png) | 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. - **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. - Click **Sanas Disabled** to review the metric for individual app user. - **Example**: App user launches and activates the Sanas app, then manually it turn off. | | **Incompatible setups** | - App users encountered system compatibility errors during the selected period. - Click **Incompatible setups** to review the metric for individual app user. - **Example**: Incompatibility error occurs when user disconnect 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:![](https://cdn.document360.io/9bc36e9c-f402-4213-b56f-4ecdf805bb1a/Images/Documentation/image(579).png) | 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. - **Example**: User logged in to the Sanas app at the beginning of their work shift. | | **Last seen** | - Timestamp of the last Sanas app activity. - **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. - The Session duration excludes any inactivity period longer than 3 hours. - **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. - 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. - **Engaged** - The Sanas app was activated and used in at least one call during the selected session. - **Not Engaged** - The Sanas app was activated but not used in any calls during the selected session. - **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. - 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). - 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. --- ### Support **Need help?** Get in touch with our [Support Team](mailto:support@sanas.ai) for assistance.