Skip to content

docs: add the audit log page - #342

Merged
jonoirwinrsa merged 9 commits into
masterfrom
docs/audit-log
Sep 11, 2026
Merged

jonoirwinrsa merged 9 commits into
masterfrom
docs/audit-log

Conversation

@jonoirwinrsa

@jonoirwinrsa jonoirwinrsa commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Documents the audit log: what it records, retention by plan, who can read it, and how to page it over the REST API.

  • New page at other-topics/audit-log.mdx, in the "Other concepts" group after request/response logging
  • Action table lists every recorded action, with what each one records
  • Retention is Hobby none / Standard 7 days / Enterprise 30 days, with a note that retention governs how far back the log can be read rather than what is captured, so an upgrade reveals history instead of starting empty
  • States plainly that inference requests are not audited, since that is the first thing people assume

Draft until the feature is generally available.

jonoirwinrsa and others added 2 commits September 7, 2026 11:34
Covers what the audit log records, retention by plan, who can read it, and how
to page it over the REST API. Every action name, retention value, and query
parameter is taken from the implementation rather than the design.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
cerebrium 🟢 Ready View Preview Sep 11, 2026, 4:39 PM

jonoirwinrsa and others added 2 commits September 7, 2026 16:17
The note told Hobby readers their activity is recorded where they cannot see
it, which reads as surveillance rather than as a reason to upgrade. The
retention table already says what each plan gets.

Replace the passing mention of the filters with a short section framed around
the questions people actually open the log to answer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Saying which roles are refused invites the reader to reason about access they
do not have. The line above already says who can read it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
How actors are persisted and resolved is ours, not the reader's. Keep the
behaviour a rename does not break attribution and drop the mechanism.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jonoirwinrsa and others added 2 commits September 11, 2026 12:35
The action table only needs to name the action. What each read hands back
is not the reader's business.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Rename and deleted-account behaviour is edge-case trivia nobody reads the
page for.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
No reason to document where the dashboard falls short. The actor parameter
is already in the API table for anyone who needs it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Drop the rationale for why each action is recorded, the note restating the
from clamp already in the table, and the pagination sentence that said
nothing. Fold the one-sentence filtering section into viewing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jonoirwinrsa
jonoirwinrsa merged commit c2047bd into master Sep 11, 2026
2 checks passed
@jonoirwinrsa
jonoirwinrsa deleted the docs/audit-log branch September 11, 2026 16:40

This branch was successfully deployed

1 active deployment
staging e6e01882 Deployed Sep 11, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants