View the audit log

In short

The audit log lists successful commands performed by human users in the organization. Filter the period, then inspect author, action, and resource to understand a change. Agent and system actions are absent from this view, while sensitive fields such as passwords, secrets, and tokens are excluded or redacted.

Expected result

You find the human action explaining a change or know that a system event must be investigated elsewhere.

Before you start

• Know the approximate period and changed resource.
• Use the log for investigation, not to copy sensitive data.

Procedure

1. Open Settings > Audit log in the relevant organization.
2. Filter a narrow period around the change time.
3. Locate the author and action name associated with the resource.
4. Open the useful entry and compare it with current object state.
5. Widen the period or contact support when no human action matches.

What Billabex does

Audit is recorded after a user command succeeds. Agent and system processing is deliberately excluded, and keys resembling password, secret, or token are redacted.

If the result is not what you expected

• A failed attempt may not appear as a successful modification.
• No human author suggests an import, workflow, or another automatic process.
• Keep the time and action name when requesting deeper investigation.