Skip to main content

Audit Logs

Track all activity in your Hublvu organization for compliance, troubleshooting, and security monitoring.

Accessing Audit Logs

Navigate to Audit Logs in the Security section of the sidebar.

What Gets Logged

User Actions

EventDescription
LoginUser authenticated successfully
LogoutUser ended session
Login FailedAuthentication attempt failed
Password ChangeUser changed password
MFA EnrolledUser set up multi-factor auth
Profile UpdateUser modified their profile

Data Changes

EventDescription
Flow CreatedNew flow created
Flow ModifiedFlow edited
Flow DeletedFlow removed
Guide CreatedNew guide created
Guide ModifiedGuide edited
Guide DeletedGuide removed
Knowledge UploadedDocument added
Knowledge DeletedDocument removed

System Events

EventDescription
Run StartedFlow or guide execution began
Run CompletedExecution finished
Run FailedExecution encountered error
Tool ExecutedExternal tool was called
Integration ConnectedNew integration configured
Integration FailedIntegration error occurred

Security Events

EventDescription
User CreatedNew user added
User DeactivatedUser access removed
Role ChangedUser role modified
Permission ChangedPermissions updated
API Key CreatedNew API key generated
API Key RevokedAPI key disabled
SSO Configuration ChangedSSO settings modified

Viewing Logs

The audit log view displays:

ColumnDescription
TimestampWhen the event occurred
UserWho performed the action
EventWhat happened
ResourceWhat was affected
DetailsAdditional context

Click any entry to see full details.

Filtering

By Time Range

  • Last 24 hours
  • Last 7 days
  • Last 30 days
  • Custom range — Select specific start and end dates

By User

Search for events by a specific user:

  1. Click Filter by User
  2. Select or search for user
  3. Apply filter

By Event Type

Filter to specific event categories:

  • User Actions
  • Data Changes
  • System Events
  • Security Events

Or filter to specific events (e.g., only "Login Failed").

By Resource

Find events related to specific resources:

  • Specific flow or guide
  • Integration name
  • File name

Exporting Logs

Export audit data for external analysis or compliance:

  1. Apply desired filters
  2. Click Export
  3. Select format:
    • CSV — Spreadsheet-compatible
    • JSON — Structured data
  4. Download file

Export Limits

Large exports are processed asynchronously. You'll receive a download link when ready.

SOC 2 Compliance

Audit logs support SOC 2 compliance requirements:

  • Comprehensive logging — All significant events captured
  • Tamper-proof — Logs cannot be modified or deleted by users
  • Retention — Logs retained per your configured policy
  • Access tracking — All data access logged

Compliance Dashboard

View compliance-specific metrics:

  1. Go to Security Analytics > Audit
  2. Review:
    • Event volume over time
    • Security event breakdown
    • User activity patterns
    • Anomaly detection

Retention

Default Retention

Audit logs are retained based on your plan:

  • Standard — 90 days
  • Enterprise — 1 year or custom

Custom Retention

Enterprise customers can configure:

  1. Go to Security Settings > Audit Configuration
  2. Set retention period
  3. Configure archival rules
  4. Save

Archived Logs

Logs beyond the active retention period may be:

  • Archived to long-term storage
  • Available on request
  • Subject to your data retention policies

Best Practices

Regular Review

Schedule regular reviews of security events, especially failed logins and permission changes.

Set Up Alerts

Configure alerts for critical events like multiple failed logins or administrative changes.

Export for Compliance

If you have compliance requirements, schedule regular exports and store them according to your data retention policy.

Investigate Anomalies

Unusual patterns (off-hours access, unexpected locations, bulk operations) warrant investigation.

Troubleshooting with Audit Logs

Finding What Changed

If something isn't working as expected:

  1. Filter by the affected resource
  2. Look for recent modifications
  3. Identify who made changes
  4. Review the change details

Tracking User Activity

To understand a user's actions:

  1. Filter by the user
  2. Review their event history
  3. Correlate with any issues or incidents

Security Investigations

For potential security issues:

  1. Filter to Security Events
  2. Look for patterns:
    • Failed logins from unusual IPs
    • Unexpected permission changes
    • Out-of-hours administrative actions