Legal & Compliance
Usage Exports
Export detailed usage analytics from your Langdock workspace to CSV format for external analysis, reporting, and compliance purposes.
Usage exports are available to workspace administrators and provide up to 12 months of historical data across users, assistants, workflows, projects, and models.
Accessing Usage Exports
Navigate to your workspace analytics page and click the Export button in the top right corner to open the export configuration dialog.1
Open Analytics
Go to your workspace analytics page in workspace settings.
2
Click Export
Select the Export button located in the top right corner
3
Configure Export
Choose your data type and date range in the export dialog
4
Generate CSV
Click Generate CSV to create and download your export file
Export Configuration
Data Types
Select which type of usage data to export:- Users - Individual user activity, message counts, and feature usage across the selected time period
- Assistants - Assistant usage statistics, interaction counts, and performance metrics
-
Workflows - Workflow execution data and usage patterns
Only available when the workflow product is enabled in your workspace (currently in closed beta; will be launched soon to all users)
- Projects - Project-level usage data
- Models - Model usage statistics and token consumption data
Date Range Options
Choose from predefined ranges or select a custom period:- This month (e.g., July 2025)
- Last month (e.g., June 2025)
- This week (e.g., July 30 - August 2)
- Last week (e.g., July 20 - July 26)
- Choose custom range - Select specific start and end dates
Historical data is limited to 12 months. You cannot export data older than 12 months from the current date.
Export Data Structure
Each export generates a CSV file with one row per entity (user, assistant, workflow, project, or model) and columns containing relevant metrics for the selected time period.Usage Exports
The Users export provides data about individual user activity within your workspace.
Column Definitions
| Column | Description |
|---|---|
period_start | Start date of the report (YYYY-MM-DD, UTC) |
period_end | End date of the report (YYYY-MM-DD, UTC) |
org_id | ID of the workspace |
user_id | ID of the user |
name | Name of the user |
email | Email of the user |
role | Role of the user (member, editor, or admin) at the time of the export |
joined_at | Date the user joined the workspace (YYYY-MM-DD, UTC) |
messages_total | Total number of messages the user has sent in the period |
messages_total_rank | Relative position of the user in a list of all workspace users sorted by total messages in the period (1 = most messages) |
messages_chat | Number of messages the user has sent in regular chats in the period |
messages_chat_rank | Relative position of the user in a list of all workspace users sorted by chat messages in the period (1 = most messages) |
messages_assistants | Number of messages the user has sent to assistant chats in the period |
messages_assistants_rank | Relative position of the user in a list of all workspace users sorted by assistant messages in the period (1 = most messages) |
assistants_messaged | Number of distinct assistants the user messaged in the period |
assistants_to_messages | JSON object mapping assistant_id to messages_count for each assistant the user messaged in the period |
messages_projects | Number of messages the user has sent to project chats in the period |
messages_projects_rank | Relative position of the user in a list of all workspace users sorted by project messages in the period (1 = most messages) |
projects_messaged | Number of distinct projects the user messaged in the period |
projects_to_messages | JSON object mapping project_id to messages_count for each project the user messaged in the period |
model_to_messages_total | JSON object mapping model_name to messages_count for each model the user messaged in the period |
action_messages | Number of messages from the user generated by actions in the period |
action_messaged | Number of distinct actions the user triggered in the period |
action_to_messages | JSON object mapping action_name to messages_count for each action the user triggered in the period. Actions include capabilities like Canvas or Web Search as well as actions from integrations |
For workspaces with user-level data disabled, certain identifying columns (like user email and name) are excluded from exports to maintain privacy compliance.
Actions Referenced in User Export
The following actions may appear in theaction_to_messages column of the Users export:
Canvas
Canvas
Used to edit documents and code in a structured interface. Messages represent user prompts that trigger Canvas interactions (creation, querying, deletion).
Web Search
Web Search
Used to search external web sources for real-time information. Messages represent user prompts that trigger web search functionality.
File Analysis
File Analysis
Used to analyze uploaded documents, spreadsheets, and other file types. Messages represent user prompts that trigger file processing and analysis.
Code Execution
Code Execution
Used to run and test code in various programming languages. Messages represent user prompts that trigger code execution requests.
Integration Actions
Integration Actions
Actions from connected integrations (e.g.,
Hubspot_create_contact, Slack_send_message). Messages represent user prompts that trigger API calls to external services through Langdock integrations.Data Handling and Privacy
Null Values
Empty or unavailable data fields are handled as follows:- Numeric fields: Display as
0or empty - Text fields: Display as empty strings
- JSON objects: Display as empty objects
{}
Data Retention
- Historical data is available for up to 12 months
- Export data reflects the state at the time of export
- User roles, names, and other attributes show values as of the period end date
BYOK Considerations
For customers using Bring Your Own Keys (BYOK):- Token usage data is available with detailed metrics
- All standard columns plus token-specific columns are included