Skip to main content

Using the Audit Log

Track administrative and system changes with searchable audit events for troubleshooting, compliance, and accountability.

Steven Silverstone
Updated by Steven Silverstone

The LinearB Audit Log enables admins to track system activity, monitor configuration changes, and support security and compliance efforts by exporting a detailed record of actions performed across the platform.

Summary
  • Audit Logs are available only to Admin users.
  • Logs can be exported in CSV or JSON format.
  • You can filter logs by a specific date range.
  • Each log entry includes who acted, what changed, when it happened, and whether the action was user- or system-initiated.
Prerequisites

Admin access is required. Only users with Admin permissions can view and generate audit logs.

Accessing the Audit Log
  1. Sign in to LinearB using an Admin account.
  2. Open Company Settings.
  3. Click Settings in the lower-left corner.
  4. Navigate to the General tab.
  5. Scroll to the bottom to find the Audit Log section.
Generating an Audit Log
  1. Select a time frame
    • Use the date picker to choose a start and end date.
    • Example: Past 30 days (Oct 4 – Nov 3).
  2. Choose a file format
    • CSV – Suitable for Excel or Google Sheets.
    • JSON – Best for developers or system ingestion.
  3. Download the log
    • Click Download Log.
    • The file is generated and saved locally.
    • Larger date ranges may take longer to process.
Audit Log Field Descriptions
  • organization_id – Unique identifier of your organization
  • team_id – Team associated with the action
  • account_id – User who performed the action
  • repository_id – Repository affected
  • created_at – Timestamp of the action
  • category – High-level action category (e.g., Authentication)
  • sub_category – Specific event type (e.g., Login)
  • description – Short explanation of the event
  • type – Source of the action
    • User – Performed by a person
    • System – Triggered automatically by LinearB
  • metadata – Key-value pairs describing what changed
    • Example: {"workingDays":{"oldValue":"1-6","newValue":"1-5"}}
Tips and Best Practices
Filtering and Analysis
  • Filter by user, team, category, or action type.
  • Use spreadsheet tools (CSV) or parsers (JSON) for analysis.
Monitoring and Security
  • Review metadata to understand configuration changes.
  • Monitor System actions to verify automations.
  • Scan logs regularly for unusual or unauthorized activity.
Storage and Compliance
  • Store audit logs securely with restricted access.
  • Encrypt files if they contain sensitive data.
  • Ensure handling aligns with your compliance requirements.
Troubleshooting
Cannot access audit logs
  • Confirm you are logged in as an Admin.
  • Verify you are viewing Company Settings.
  • If issues persist, contact LinearB Support.
Slow generation or download
  • Large date ranges take longer to process.
  • Try exporting a shorter time window.
File format issues
  • Use Excel or Google Sheets for CSV files.
  • Use a JSON viewer or text editor for JSON files.

How did we do?

Understanding Users and Contributors in LinearB

⭐ Start Here — Recommended

Contact