Skip to main content
Activity Logs view Activity Logs (also called Audit Logs) provide a complete audit trail of all actions taken within your workspace, helping you track changes, debug issues, and maintain security compliance.

​
What are Activity Logs?

Activity Logs record every significant action in your workspace:
  • Workspace Changes: Creation, deletion, and configuration updates
  • Playbook Activity: Creation, updates, and executions
  • Toolbox Actions: Server installations, uninstalls, and restarts
  • API Token Management: Token creation and deletion
  • User Actions: Who performed each action and when

​
Log Overview

Activity logs overview The Activity Logs page displays:
​
Total Actions
number
Count of all logged actions in the selected time period
​
Success Rate
percentage
Percentage of actions that completed successfully
​
Successful
number
Count of successful actions
​
Failed
number
Count of failed actions

​
Filtering Logs

Use filters to find specific activities:

​
By Status

​
All Status
default:true
Show all log entries
​
Success
Show only successful actions
​
Failed
Show only failed actions

​
By Resource Type

Filter by the type of resource that was acted upon:
  • All Resources: Show everything
  • Workspace: Workspace creation and updates
  • Assistant: AI assistant interactions
  • Playbook: Playbook operations
  • Toolbox: MCP server management
  • API Token: Token management
  • Organization: Organization-level changes
  • Settings: Configuration updates

​
By Time Range

​
All Time
Show all historical logs
​
Last 24 Hours
Recent activity from the past day
​
Last 7 Days
Activity from the past week
​
Last 30 Days
default:true
Activity from the past month (default)
​
Last 90 Days
Activity from the past quarter

​
Search Logs

Use the search box to find specific:
  • User names
  • Resource names
  • Actions
  • IP addresses

​
Log Entry Details

Each log entry shows:

Icon

Visual indicator of the action type
  • 🏢 Workspace
  • ▶️ Execution
  • ✏️ Update
  • 📋 Creation
  • ⬇️ Installation

User

Who performed the action (name and email)

Action

What was done (e.g., “Created playbook”, “Installed tool”)

Resource

The resource that was affected (name in quotes)

Timestamp

When the action occurred (relative and absolute time)

Resource Type

The category of the resource (workspace, playbook, toolbox)

IP Address

The IP address from which the action was performed

Status

Success indicator (✅) or failure (❌)

​
Expanding Log Entries

Click on a log entry to see additional details:
  • Full timestamp
  • Complete resource path
  • Error messages (if failed)
  • Related resources
  • Request metadata

​
Common Log Actions

​
Workspace Actions

  • Created workspace: New workspace was created
  • Updated workspace: Workspace settings were modified
  • Deleted workspace: Workspace was permanently removed

​
Playbook Actions

  • Created playbook: New playbook was created
  • Updated playbook: Playbook instructions or configuration changed
  • Executed playbook: Playbook was run
  • Deleted playbook: Playbook was removed

​
Toolbox Actions

  • Installed tool: MCP server was installed from catalog
  • Uninstalled tool: MCP server was removed
  • Restarted tool: MCP server was restarted
  • Configured tool: Server settings were updated

​
Token Actions

  • Created token: New API token was generated
  • Deleted token: API token was revoked

​
Using Logs for Debugging

Activity Logs help diagnose issues:
1

Identify the Problem

Note when the issue started occurring
2

Filter by Time

Set the time range to cover the period when the issue began
3

Filter by Resource

Select the resource type related to the issue (e.g., Playbook, Toolbox)
4

Look for Failures

Filter by “Failed” status to see what went wrong
5

Review Details

Click on failed entries to see error messages and context

​
Exporting Logs

Export logs for compliance or offline analysis:
1

Apply Filters

Set filters to select the logs you want to export
2

Click Export

Click the Export button in the top right
3

Choose Format

Select format (CSV or JSON)
4

Download

Download the exported file
Exported logs include all visible columns plus additional metadata not shown in the UI.

​
Retention Period

Logs are retained for 30 days
Logs are retained for 90 days
Logs are retained for 1 year or custom retention period

​
Security & Compliance

Activity Logs support:

Audit Trail

Complete record of all workspace changes

User Attribution

Track who made each change

IP Tracking

Record the source IP for all actions

Compliance

Meet SOC 2, ISO 27001, and GDPR requirements

​
Troubleshooting

  • Refresh the page: Click the “Refresh” button
  • Check filters: Make sure filters aren’t too restrictive
  • Check time range: Expand the time range to see older logs
  • Use search: Try searching for the resource name or user
  • Check resource type: Make sure the correct resource filter is selected
  • Expand time range: The action might be older than the current filter
  • Check permissions: Make sure you have export permissions
  • Reduce filter range: Try exporting a smaller time range
  • Try different format: Switch between CSV and JSON

​
Best Practices

Review activity logs weekly to catch unexpected changes or security issues
Set up alerts for failed actions that indicate system issues
Regularly export logs for long-term archival and compliance
Save time by using resource type and status filters to focus on relevant logs

Playbooks

View playbook execution logs

Toolbox

Track server installations and changes

Workspace Management

Manage workspace access and security

API Tokens

Track token creation and usage
⌘I