Audit log

Who submitted, who was refused, and who changed what.

Administrators only. A searchable record of the actions that matter after the fact.

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.

The audit log 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.