Skip to main content

Audit & Change History

Track all changes made to feature flags, experiments, and configurations with Toggly's audit logs and change history.

Audit Logs​

Audit logs provide a complete record of all activities in your Toggly account.

Viewing Audit Logs​

  1. Navigate to Audit Logs in the dashboard
  2. Use filters to find specific events:
    • Date Range: Filter by time period
    • User: Filter by who made the change
    • Action Type: Filter by type of action
    • Resource: Filter by feature flag, experiment, etc.
  3. Click on any log entry to see detailed information

Audit Log Information​

Each audit log entry includes:

  • Timestamp: When the action occurred
  • User: Who performed the action
  • Action: What action was taken (create, update, delete)
  • Resource: What was changed (feature flag, experiment, etc.)
  • Before/After: Previous and new values (for updates)
  • IP Address: Source IP address of the action
  • User Agent: Browser or client information

Change History​

View the complete change history for any feature flag or experiment.

Feature Flag History​

  1. Navigate to a feature flag
  2. Click the History tab
  3. View all changes made to the flag:
    • Status changes (enabled/disabled)
    • Targeting rule updates
    • Description changes
    • Configuration modifications

Experiment History​

  1. Navigate to an experiment
  2. Click the History tab
  3. View experiment lifecycle:
    • Experiment creation
    • Configuration changes
    • Start/stop events
    • Results and decisions

Filtering and Searching​

Date Range Filters​

Filter audit logs by date:

  • Last 24 Hours: Recent changes
  • Last 7 Days: Week of changes
  • Last 30 Days: Month of changes
  • Custom Range: Specific date range

User Filters​

Filter by who made changes:

  • Specific User: See all changes by a user
  • User Role: Filter by user role (admin, developer, etc.)
  • Team: Filter by team or department

Action Type Filters​

Filter by type of action:

  • Create: New resources created
  • Update: Existing resources modified
  • Delete: Resources deleted
  • Enable/Disable: Feature flag state changes

Resource Filters​

Filter by what was changed:

  • Feature Flags: Changes to feature flags
  • Experiments: Changes to experiments
  • Segments: Changes to segments
  • Settings: Configuration changes

Exporting Audit Logs​

Export audit logs for compliance or analysis:

  1. Navigate to Audit Logs
  2. Apply filters if needed
  3. Click Export
  4. Choose format (CSV or JSON)
  5. Download the file

Export Formats​

  • CSV: Spreadsheet format for analysis
  • JSON: Machine-readable format for processing

Audit Log Integrity Verification​

Every audit event stored in Toggly includes a cryptographic integrity hash (HMAC-SHA256). When you open Audit Event Details in the timeline, Toggly verifies that hash on read and shows one of three states:

StatusMeaning
Integrity verifiedThe stored hash matches a recomputed hash for the event payload. The record has not been altered since it was written.
Integrity check failedA hash is present but verification failed. Treat the entry as potentially tampered and investigate.
Integrity not verifiedVerification does not apply to this row.

When integrity is not verified​

Integrity verification applies only to events loaded from AuditEvents. The following entries are shown in the audit timeline but do not receive integrity verification:

  • Environment:DeploymentDetected — Synthetic deployment rows built from environment deployment history. They are not backed by an audit document and have no integrity hash.

All other audit events in the timeline are backed by stored audit documents with integrity hashes and are verified when you view their details.

API field​

Audit API responses include integrityValidated:

  • true — hash verified successfully
  • false — hash present but verification failed
  • null — not applicable (synthetic deployment entry)

Compliance​

Audit logs help with compliance requirements:

  • SOC 2: Security and availability controls
  • GDPR: Data processing records
  • HIPAA: Healthcare data access logs
  • PCI DSS: Payment card data access

Best Practices​

1. Regular Reviews​

Review audit logs regularly to:

  • Detect unauthorized access
  • Understand change patterns
  • Debug issues
  • Ensure compliance

2. Set Up Alerts​

Configure alerts for critical actions:

  • Feature flag deletions
  • Permission changes
  • API key revocations
  • Experiment modifications

3. Export Regularly​

Export audit logs periodically for long-term storage and compliance.

4. Monitor Access​

Watch for unusual access patterns or unauthorized changes.

Next Steps​