Audit Trail and Diagnostics
Choose the right audit or diagnostic tool for user actions, settings changes, authentication events, schema checks, and telemetry.
Use audit and diagnostics pages when you need to investigate who changed something, why an integration failed, or whether the database shape matches what an admin workflow expects.
Before you begin
You need an admin role with access to audit or settings diagnostics.
Before investigating, collect the approximate time window, user or API client, resource ID, page or workflow, and whether you are investigating a user action, settings change, authentication event, or schema/debug issue.
Choose the audit task you need
Use the focused guide that matches the job:
- Review Audit Logs for platform audit events, settings change history, and authentication/API access logs.
- Use Diagnostic Tools for Schema Inspector and Telemetry.
- Investigate Admin Activity for common investigation paths.
Verify success
An audit or diagnostic review is complete when:
- The time window is narrowed to the relevant event range.
- Filters identify the user, resource, category, client, or setting key.
- You can explain what changed or why the event failed.
- Any CSV export contains the relevant rows.
- Follow-up work is assigned to the correct owner.
Troubleshooting
Expand the date range first. Then remove category, user, and resource filters. If events still do not appear, confirm your organization context and permissions.
Use Authentication Audit Logs under API Access. That page is focused on authentication events and exposes status, client ID, IP address, and error details.