> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuneplane.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit

> Who submitted, who was refused, and who changed what, at /admin/audit.

A searchable record of the actions that matter after the fact, at `/admin/audit`.

Administrators **and auditors**. It is the one page in the admin area with a wider audience: an
auditor reaches this and nothing beside it, which is what lets somebody read the trail without
being able to act on the platform.

![TunePlane audit log](https://mintcdn.com/starforge/GatXR2rI5-_Vm4_H/images/console/audit.png?fit=max\&auto=format\&n=GatXR2rI5-_Vm4_H\&q=85\&s=035764a583529ee7c4abd3a3bbdadd6a)

The audit log: user, action, object and source address.

## What is recorded

| Action | Recorded because |
| - | - |
| Submit job / submit denied (quota) | The two halves of "why did this not run" |
| Create user, set role, enable or disable user | Who has access, and who granted it |
| Set quota | Capacity decisions, with a person attached |
| Stop job, delete job, bulk stop, clean up jobs | Destructive actions on somebody else's work |
| Create or revoke a share link | The one path that moves data outside authentication |
| Create or revoke a review share link | Same, for a comparison |
| Update, rename or delete a project | Structural changes others depend on |

Each entry carries the user, the action, the object and the time. Search matches across user, action
and object.

## What it is for

Two questions, in practice.

**"Why did my job not run?"** — a refusal at admission is recorded with the gate that refused it, so
the answer survives past the moment the error message scrolled away.

**"Who stopped my run?"** — stops, deletions and bulk cleanups are attributed. On a shared cluster
this is what keeps an operational action from becoming an accusation.

> [!NOTE]
>
> The trail records control-plane actions, not training content. It will tell you that somebody
> submitted a job and what its id was; it will not tell you what was in the data.

## What it is not

Tamper-**evident**, not tamper-proof. Entries are append-only and an alteration is detectable,
which is what an assessment asks for. An operator with database access can still reach the rows;
what they cannot do is change one without that being visible.

## Next

[Users](https://docs.tuneplane.ai/en/console/users.md) · [Sharing](https://docs.tuneplane.ai/en/guides/sharing.md) ·
[Observability](https://docs.tuneplane.ai/en/ops/observability.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.