Skip to content
AletheiaAletheiaAletheia docs

AI audit log

The AI audit log (/admin/ai-audit) records what was asked, what was answered, and exactly which queries ran in between.

What an entry contains

Section titled “What an entry contains”

Each entry is one exchange:

  • The question and who asked it.
  • The answer, with the evidence it cited.
  • Every query the assistant ran: which one, the arguments it was called with, a summary of what came back, whether it succeeded, and how long it took.
  • The conversation it belongs to.

Denied queries are recorded as denied. If the assistant tried to read something the asker was not allowed to see, the log shows the attempt and the refusal rather than omitting it.

Why the queries are recorded

Section titled “Why the queries are recorded”

Reviewing an AI feature usually founders on not being able to tell what it actually looked at. Recording every query with its arguments makes that answerable: you can confirm the assistant only ever ran read queries, only ever within your organization, and only ever within the asker’s permissions.

It is also how you check a surprising answer. If the answer looks wrong, the queries behind it usually explain why.

Filtering

Section titled “Filtering”

Filter by user, by conversation, or by time range, and page back through the history.

Access

Section titled “Access”

Reading the AI audit log needs the audit-read permission — the same one that governs the organization audit log. Being able to use the assistant does not let you read what other people asked it.

Retention and immutability

Section titled “Retention and immutability”

Entries are append-only. They cannot be edited or deleted, including by an administrator, and the database enforces that rather than trusting the application.

Turning the assistant off does not clear the log. The record of what was asked while it was enabled survives.

Where to go next

Section titled “Where to go next”