# Activity & audit (/docs/activity)

The activity trail stays with the organization even when agent runtimes are
short-lived. Use [Dashboard → Activity](https://app.corespeed.io/activity) to
inspect recent tool and control-plane actions.

## Visibility \[#visibility]

* Members see actions attributed to themselves.
* Organization administrators see activity across the organization.
* Non-admin views do not expose IP address or user-agent metadata.

API-key activity is attributed through the key's owning identity so the same
organization and member rules still apply.

## What the trail records \[#what-the-trail-records]

Activity records identify the action, actor, organization, outcome, surface,
request, and time. Where a billable action has a charge, the dashboard joins it
to the billing ledger to display cost; the audit event itself is not the money
authority.

A tool call's record says how it ended — `ok`, `error`, `held` (a billing hold
or a pending approval), or `denied` — and, for a failure, its `code` and
the text the agent was shown, bounded to 512 characters. A call refused
before any tool ran (an unknown tool, invalid arguments) leaves no record; the
client already has its answer.

Sensitive request content is not copied into the trail. Metadata is redacted
before enqueueing, detail is bounded, and prompts are not treated as audit
payloads.

## Delivery behavior \[#delivery-behavior]

Activity emission is asynchronous and fail-open for the product action: a
temporary audit-pipeline failure does not repeat or roll back an already valid
connector call. Retries, deduplication, and a dead-letter path protect the
recording pipeline separately.