TutorCat Guide Open TutorCat

Admins

The audit log

Every admin change, who made it, when, and the written reason. Append-only.

On this page
  1. How entries get there
  2. Read the table
  3. Filter and export
  4. Write reasons that will make sense later

The Audit log is the record of every admin change: who made it, what it was, what it changed, and the reason they wrote. It is append-only: the database itself refuses any edit or deletion of an entry, whoever tries.

The Audit log with Actor and Type filters, Export CSV and an opened before/after
  1. Filter by admin
  2. Filter by action
  3. Save the log
  4. The written reason
  5. Value before and after

How entries get there

  • The entry is written before the change takes effect.
  • If the entry cannot be written, the change is refused and nothing happens.
  • If the change fails after the entry is written, the entry stays. A failed attempt is still on record.
  • A change without a reason is refused.

Read the table

Column Meaning
When Date and time, for example 24 Oct 09:12.
Actor The admin who made the change, as the first eight characters of their account id. system for changes the platform made by itself. Hover for the full id.
Action What happened, as a coloured pill, with the target next to it (a setting key, an invite code, an account id).
Reason What the admin wrote. Select before / after to see the values before and after the change.

The actions you will see:

Action Made by
update_setting, clear_setting Saving or clearing a setting, including the budget, registration and model prices.
suspend_user, unsuspend_user, erase_user The account actions on Users.
create_invite, revoke_invite Invites.
create_package, update_package, archive_package Packages.
update_pricing Pricing.
update_model_assignment The speech-to-text model.
update_ai_route A job's model chain on Models.
sync_ai_catalog Sync models on Models.
run_safety_eval A safety test started on Models.

Secret settings (keys and passwords) are never written into the log. Their before and after only say whether a value was set, for example {"configured": true}.

Filter and export

  • Actor and Type narrow the rows already loaded.
  • Load older at the bottom loads the next 50 entries.
  • Export CSV saves the log as a spreadsheet file, for the weekly review or for counsel.

Write reasons that will make sense later

Someone reading the log in six months should understand the change without asking you.

  • Good: "Raised daily budget for beta wave 2: 8 more families from Monday."
  • Not enough: "budget".
  • Never: a family's email address, a child's name, or anything a child wrote.