Skip to main content
The organization Audit Log records terminal write outcomes from supported Forge activity, including user actions, agent tool actions, external system writes, and selected application changes. Use it to answer:
  • who or which agent initiated the action;
  • which system and tool were involved;
  • which ticket or other target was affected;
  • whether the action succeeded or failed;
  • when the terminal outcome occurred.

​
Investigate an action

1

Set the time window

Start narrowly around the reported change.
2

Filter the actor or system

Distinguish a user action from a background agent or platform workflow.
3

Search the target

Use the exact ticket or supported target identifier when available.
4

Read the outcome

Identify the tool, status, and sanitized metadata.
5

Verify externally

Check the authoritative PSA or connected system for the resulting state.
6

Follow the workflow

Open the related Chat, ticket, project, agent run, or AI Engineer run for reasoning and context.

​
What the log does not contain

The Audit Log is designed to record attributable outcomes without copying raw sensitive tool arguments, provider responses, error bodies, or executed code into the log. It is not a full replacement for the source provider’s own audit history.
Read-only searches are not the primary purpose of this log. Use the relevant workflow history and provider records when investigating how a conclusion was formed.

​
Review rhythm

Administrators should sample successful writes as well as failures, investigate repeated errors, compare background behavior to configured Availability, and use findings to improve roles, mappings, runbooks, skills, and agents.