Logs
The Logs page is your central hub for monitoring conversations, messages, and usage across your AI Assistant. Here you can track activity, analyze performance, and control how data is stored and who can access it.
You need to have an AI Assistant created to access the Logs functionality. If you haven't created one yet, check the Create an AI Assistant section first!
Only conversations from AI Assistant chat tasks are recorded in logs. Conversations made in the main chat playground are never logged, regardless of your saving policy settings. The logs feature only tracks interactions that happen within your specific AI Assistant's chat interface.
Conversation Saving Policy
The conversation saving policy determines how your AI Assistant handles and stores user interactions within the AI Assistant's chat task. This is crucial for compliance, privacy, and functionality. You can choose from three different approaches:
Remember: This policy only applies to conversations within your AI Assistant's chat interface. The main chat playground conversations are never logged.
- Store All
- Discard All
- Store Anonymized
All conversations are saved and accessible to users of this assistant.
This option preserves the complete conversation history, making it ideal for:
- Team collaboration - All team members can see the full context
- Knowledge continuity - Previous discussions remain available for reference
- Training purposes - Complete interaction history for analysis
- Customer support - Full context of user issues and solutions
Conversations are not saved.
This option ensures maximum privacy by not storing any conversation data:
- Complete privacy - No conversation data is retained
- Testing environment - Perfect for development and testing
- Compliance - Meets strict data protection requirements
Conversations are saved without user identities and accessible to users of this assistant.
This balanced approach provides analytics while protecting user privacy:
- Privacy protection - User identities are removed from stored data
- Analytics enabled - Content analysis without personal information
- Public assistants - Ideal for publicly accessible AI assistants
- Compliance friendly - Meets many data protection standards
The saving policy determines what data exists to be logged. If you choose Discard All, there will be no logs to display regardless of your visibility settings. Think of it as: Saving Policy = "What gets stored" and Visibility Settings = "Who can see what's stored".
Visibility Settings for Logs
Once you've decided what data to store, you can control who has access to view the logs. This is separate from your saving policy and gives you fine-grained control over data access:
- Share with All AI Assistant Users — All users of this assistant can view the logs and conversation history
- Not Shared — Logs are completely private and not visible to anyone
- Share with the AI Assistant Owner — Only the assistant owner (typically the creator) can view the logs
Quick Reference Matrix
Here's a quick overview of how your saving policy and visibility settings work together:
| Saving Policy → / Visibility ↓ | Store All | Store Anonymized | Discard All |
|---|---|---|---|
| Share with All AI Assistant Users | Everyone sees full logs | Everyone sees anonymized logs | No logs exist |
| Share with the AI Assistant Owner | Only owner sees full logs | Only owner sees anonymized logs | No logs exist |
| Not Shared | No one sees logs | No one sees logs | No logs exist |
Why Use Logs?
The logs feature provides valuable insights into how your AI Assistant is performing and being used through its dedicated chat interface. Here are the key benefits:
Scope of Logging: Logs only capture conversations that happen within your AI Assistant's chat task, not the main chat playground. This focused approach helps you track the specific performance and usage of your trained assistant.
- Activity Monitoring — Track message and conversation volumes to understand usage patterns
- Data Source Analysis — Identify which data sources are most frequently accessed and useful
- Quality Assurance — Find and address unanswered messages to improve user experience
- User Engagement — Analyze usage patterns and trends to optimize your assistant
- System Health — Monitor performance metrics and identify potential issues
- Compliance — Maintain records for audit trails and regulatory requirements
Logs Dashboard Features
The logs dashboard is your command center for monitoring and managing your AI Assistant's activity. Here's what you can do:
Overview & Analytics
The main dashboard gives you a comprehensive view of your assistant's performance:
- Key Metrics — Total conversations, messages, and active users
- Activity Charts — Visual trends over time to spot patterns
- Current Settings — Your active Saving Policy and Visibility Settings at a glance
- Real-time Updates — Live monitoring of current activity
Message Sources Analysis
Track which data sources are being used most effectively:
- Source Usage Stats — See which files and documents are accessed most frequently
- Export Capabilities — Download usage data for further analysis
- Customizable Columns — Configure the table to show the metrics that matter to you
- Performance Insights — Identify which sources provide the best answers
Messages Without Answers
Identify and improve areas where your assistant struggles:
- Failed Responses — See messages that didn't receive satisfactory answers
- Context Analysis — Understand why certain questions weren't answered
- Q&A Creation — Convert problematic interactions into new Q&A entries
- Continuous Improvement — Use this data to enhance your assistant's knowledge base
User Management
Monitor and manage your assistant's user base:
- User Directory — Complete list of users who have interacted with your assistant
- Usage Statistics — Conversation counts and engagement levels per user
- Geographic Data — Location information (when available) for user analytics
- Account Management — First-seen dates and user activity tracking
- Data Control — Delete logs for specific users when needed
Best Practices
To get the most out of your logs while maintaining security and compliance:
Choosing the Right Settings
- Store All — Best for internal teams where full context is valuable
- Store Anonymized — Ideal for public assistants or when privacy is important
- Discard All — Perfect for testing environments or strict privacy requirements
Visibility Guidelines
- Set Visibility to match your compliance model (follow the principle of least access)
- Consider your organization's data governance policies
- Regularly review who has access to sensitive conversation data
Remember: Saving Policy = "What gets stored" and Visibility Settings = "Who can see what's stored". These work together to give you complete control over your data.