Audit log for trees and facts

Created by Certorix Online, Modified on Mon, 4 May at 9:27 PM by Certorix Online

Audit log

Certorix maintains an audit log of all significant actions in your organization. Available for Pro and Business plans.

What is logged

  • Tree actions – Create, edit, publish, unpublish, delete, restore, export, import, version snapshot saved, version restored.
  • Fact actions – Create, edit, certify, uncertify, delete, restore, AI summary generation.
  • User actions – Login, logout, password change, 2FA enable/disable, API token regeneration.
  • Team actions – Invite sent, invite accepted, role changed, member removed.
  • Billing actions – Plan upgrade, plan downgrade, payment method added, subscription cancelled.
  • Freshdesk actions – KB sync, connection test, article import.

Accessing the audit log

  1. Go to SettingsAudit log (sidebar, under Account).
  2. Select a date range (default: last 7 days).
  3. Filter by action type (optional).
  4. Filter by user email (optional).

Audit log entry details

Each entry includes:

  • Timestamp – When the action occurred (UTC).
  • User – Email of the user who performed the action.
  • Action – Type of action (e.g., 'tree.published', 'fact.certified').
  • Resource – ID and name of affected tree/fact (if applicable).
  • IP address – IP address of the user at the time of action.
  • User agent – Browser and OS information.
  • Details – JSON field with additional context (e.g., previous value, new value, error message if failed).

Retention period

  • Pro plan – 90 days of audit log retention.
  • Business plan – 1 year of audit log retention.
  • Free plan – Audit log not available.

Exporting audit log

Click Export CSV to download the current filtered view as a CSV file for analysis in Excel or external SIEM tools.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article