This article outlines what’s included in workspace analytics and how to navigate the dashboard to understand adoption and engagement across your workspace.
For guidance on how to operationalize these insights (playbooks, enablement motions, champion programs), see our Academy guide: ChatGPT Enterprise workspace analytics guide
Overview
Workspace analytics in ChatGPT Enterprise and Edu provides a workspace-level view of adoption and usage so you can monitor trends, identify patterns, and report progress over time.
Accessing workspace analytics
In ChatGPT Enterprise or Edu:
Go to Workspace settings > Workspace analytics.
Permissions
Viewing workspace analytics is available to:
Members with the analytics viewer role
Workspace admins
Workspace owners
Workspace analytics dashboard sections
Overview
Use Overview for a quick health check of adoption and engagement. It provides trend views that help you understand how usage changes over time, including:
Unique active users
Total messages
GPT messages
Tool messages
Project, app, and skill usage trends
Breakdowns by SCIM groups, when configured
If your workspace has enabled SCIM, analytics views can be segmented by the groups that are synced from your identity provider. Using SCIM groups that represent real organizational units (such as teams or departments) can help enable more meaningful analytics breakdowns.
To learn more about SCIM, please see our collection of articles on SSO, SCIM, and User Management.
Benchmarks
Use Benchmarks to compare key adoption and engagement signals against an industry median:
Activation rate
WAU (weekly active users) per activated user
Messages per WAU
You can select a benchmark industry from the in-product dropdown.
Impact
Use Impact to understand workspace-level outcomes reported through optional in-product surveys.
Impact surfaces aggregated, self-reported signals from the Impact survey that help teams understand how ChatGPT affects work across the organization, including:
Share of respondents reporting positive impact on productivity, time saved, work quality, work satisfaction, ability to complete new tasks, and stakeholder service
Per-question response distributions
Survey participation rate (respondents as a share of workspace members)
These signals are intended for directional analysis and organizational insight. They are not compliance logs and do not represent a causal ROI measurement.
For more information on impact surveys, see: Managing impact surveys in workspace analytics.
Task insights
Task insights shows aggregated patterns of work in ChatGPT by classifying conversations into broad task categories and topics. It provides workspace-level insights without exposing individual prompts, conversations, or user-level activity.
Task type
The Task type section shows the distribution of conversations across task categories, helping you quickly understand the most common ways ChatGPT is used in your workspace and how those patterns change over time.
Heat map
The Heat map compares task types across a second dimension so you can analyze usage patterns in more detail. Depending on available data, it shows how task types relate to conversation topics or organizational units.
Note: SCIM groups with fewer than 10 members will not appear as a row in the task insights heat map.
Disabling task insights
The Task insights tab and conversation classification are enabled by default. Workspace admins and owners may opt out by:
Go to Workspace settings
Scroll to the Workspace analytics section under the General tab
Turn off Enable task insights
Users
The Users section helps with license and engagement tracking:
Seats purchased
Seats enabled
Active users
Pending invites
Per-user usage metrics (for example: total, GPT, tool, project, and connector activity)
Power users (your most engaged users: top 20% message senders with 75+ messages/week and 3+ different tools per month)
GPTs
GPT analytics includes:
Total GPTs
GPTs created in period
GPTs active in period
GPT-level usage and reach metrics
Projects
Project analytics includes:
Total projects
Projects created in period
Projects active in period
Project-level usage and reach metrics
Skills
Skills analytics includes:
Skill usage trends
Top skills by message activity
Export
Use Export to generate on-demand CSV reports for the following data types:
GPTs
Impact survey
Projects
Users
For Users, GPTs, and Projects exports, select a preset date range or select Custom to choose a start date and end date. Custom export ranges can cover up to 12 months and cannot end after the current date.
Non-CSV export formats and additional tabs are not currently supported.
Generate a CSV report
Go to Workspace settings > Workspace analytics.
Select Export data.
Select a Data type.
Select a preset Date range, or select Custom and choose a start date and end date.
Select Generate CSV.
Data coverage and limitations
Workspace analytics is an aggregated analytics experience. It is not a raw log interface and does not expose:
Message text
File contents
Item-level compliance records
For raw logs, legal/security workflows, and compliance controls, use the Compliance API.
Data freshness
Workspace analytics is not real-time. Data is refreshed regularly every 1–24 hours, typically landing within a 6–12 hour range, with a 48-hour SLA. Use the last updated timestamp for confirmation. Last updated timestamp currently uses UTC timezone.
Workspaces with EU data residency
In workspaces with EU data residency, Task insights is disabled by default. A workspace owner can enable the feature at any time in Workspace settings.
Once enabled, ChatGPT will begin generating aggregate Task insights data for the workspace. If Task insights is later disabled, new Task insights data will stop being generated. Previously generated aggregate data is currently not deleted.
FAQ
Can I segment analytics by team, department, or business unit?
Some workspace analytics views support segmentation by SCIM groups, which can represent teams, departments, or business units depending on how your identity provider has been configured. If you need additional breakdowns, you can export reports and combine them with your internal data.
Can I change the impact survey or make my own?
Workspace owners can create an Admin-created survey from the Impact tab, but they can’t customize the survey questions or answer choices. Admin-created surveys use the same built-in question set as OpenAI-created surveys. For more information, see: Managing impact surveys in workspace analytics.
Can I export the Task insights reports?
No. We are actively working on this and hope to introduce this ability in a future update.
Why don’t Compliance API counts match workspace analytics?
Counts can differ because the Compliance API returns raw system data, while Workspace Analytics reports cleaned analytics data. For example, the API may include internal system messages or records without timestamps that analytics excludes.
What’s the difference between “Filter by Group” in Overview and “All organizational units” in Task insights?
In Overview, the dropdown menu Filter by Group includes all groups available in the workspace, including both SCIM-managed groups and groups created in the ChatGPT UI.
In Task insights, the dropdown menu All organizational units includes only SCIM groups. In this view, organizational units correspond to SCIM groups.
What if my workspace doesn’t use SCIM?
If your workspace does not use SCIM, admins do not need to manually create or map groups for Task insights. Instead, Task insights shows an alternate view based on the intersection of Task type and Conversation topic, rather than organizational units.
Conversation topics are automatically generated and may include categories such as Sales or Engineering.
Appendix: Export data reference
The following tables describe the columns included in current export files.
Common columns in every export
| Column | Description |
| cadence | The reporting period type. Current values include Weekly, Monthly, Partial Weekly, Partial Monthly, and Date Range. |
| period_start | The start date of the reporting period. |
| period_end | The end date of the reporting period. For partial periods, this reflects the latest available end date in the export. |
| account_id | The workspace account ID associated with the report. |
User report
A per-user workspace usage report for the selected period. It combines user identity and status fields with aggregate usage metrics for messages, GPTs, tools, and projects.
| Column | Description |
| public_id | The public ID associated with the user. |
| name | The user’s name. This may be blank for pending users. |
| The user’s email address. | |
| role | The user-entered onboarding role. |
| user_role | The workspace role as of period end. |
| department | The user-entered onboarding department. |
| groups | Group membership data for the user as of period end. |
| user_status | The user record status as of period end. |
| created_or_invited_date | The date the user was provisioned or invited. |
| is_active | Whether the user sent at least one message during the reporting period. |
| first_day_active_in_period | The first day the user was active in the reporting period. |
| last_day_active_in_period | The last day the user was active in the reporting period. |
| messages | Total messages sent by the user in the period. |
| messages_rank | Rank by total messages within the workspace for the period. |
| model_to_messages | JSON map of model family to message count. |
| gpt_messages | Messages the user sent to custom GPTs in the period. |
| gpts_messaged | Number of distinct custom GPTs the user messaged in the period. |
| gpt_to_messages | JSON map of GPT ID to message count. |
| tool_messages | Tool-generated message count associated with the user in the period. |
| tools_messaged | Number of distinct tools used in the period. |
| tool_to_messages | JSON map of tool name to message count. |
| project_messages | Messages the user sent inside projects in the period. |
| projects_messaged | Number of distinct projects the user contributed to in the period. |
| project_to_messages | JSON map of project ID to message count. |
| projects_created | projects created by the user in the period. |
| last_day_active | The last day the user was active in this or any prior period. |
| credits_used | Optional field that may appear for eligible workspaces where credit balance data is included. |
GPT report
A per-GPT workspace usage report for the selected period. It shows GPT identity, creator metadata, activity, and usage within the workspace.
| Column | Description |
| gpt_id | The custom GPT ID. |
| gpt_name | The GPT name as of period end. |
| config_type | The GPT config state. Current raw values in code are live and draft. |
| gpt_description | The GPT description as of period end. |
| gpt_url | The GPT URL. |
| gpt_creator_public_id | The public ID of the GPT creator. |
| is_active | Whether the GPT received at least one message in the period. |
| first_day_active_in_period | The first day the GPT was active in the period. |
| last_day_active_in_period | The last day the GPT was active in the period. |
| messages_workspace | Messages sent to the GPT within your workspace in the period. |
| unique_messagers_workspace | Count of distinct workspace users who messaged the GPT in the period. |
| gpt_creator_email | The creator email, when available. |
Project report
A per-project workspace usage report for the selected period. It mirrors the GPT export structure, but with project-specific identifiers and creator metadata.
| Column | Description |
| project_id | The project ID. |
| project_name | The project name as of period end. |
| config_type | The raw config state from the analytics source. |
| project_description | The project description as of period end. |
| project_url | The project URL. |
| project_creator_public_id | The public ID of the project creator. |
| is_active | Whether the project received at least one message in the period. |
| first_day_active_in_period | The first day the project was active in the period. |
| last_day_active_in_period | The last day the project was active in the period. |
| messages_workspace | Messages sent inside the project within your workspace in the period. |
| unique_messagers_workspace | Count of distinct workspace users who contributed to the project in the period. |
| project_creator_email | The creator email, when available. |
Impact survey report
A response-level export of Impact survey data for the selected workspace. Based on the exported fields, each row represents one answered survey question for one respondent.
| Column | Description |
| date_partition | The date associated with the survey response row. |
| workspace_id | The workspace account ID associated with the response. |
| name | The respondent’s name. |
| The respondent’s email address. | |
| survey_id | The survey ID. |
| survey_name | The survey name. |
| question_id | The survey question ID. |
| answer_id | The selected answer ID for that question. |