Skip to main content

Audit logs

Audit logs help Builders understand what changed in an app, who changed it, and when it happened.

Switera audit logs page with filters and CSV or JSON export actions
Use audit logs after setup changes, failed workflows, key rotation, or security-sensitive actions.

When to open audit logs​

Open Admin > Audit Logs when you need to answer:

  • who changed an Auth setting?
  • when was an API key rotated?
  • who created or edited an organization?
  • was a webhook endpoint changed?
  • did a setup action happen in the wrong app?
  • what changed before a user-visible issue started?

Filter activity​

Use filters to narrow the log:

FilterUse it for
Action or event typeFind one kind of change.
ActorFind changes by a specific Builder or system actor.
Date fromStart an investigation window.
Date toEnd an investigation window.

Set a narrow time range first. Expand only if the expected event is not visible.

Export logs​

Use CSV for spreadsheet review. Use JSON for automation, support tooling, or deeper investigation.

Export only what you need. Audit logs can contain operational context and should be handled as internal operational data.

Investigation workflow​

  1. Open the affected app.
  2. Open Admin > Audit Logs.
  3. Filter by the approximate time window.
  4. Search for the affected area, such as Auth, email, webhook, organization, or key.
  5. Identify the actor and event.
  6. Compare the current setting with the expected setting.
  7. Revert the change if safe.
  8. Rotate credentials if a secret may have been exposed.

What not to put in public tickets​

Do not paste:

  • passwords
  • provider secrets
  • API secret keys
  • private tokens
  • full exported user lists
  • raw sensitive log payloads

Include only the minimum context needed for support or engineering review.

Related pages: