Skip to content
Plugboard docs

AI activity

Admin, AI activity. Requires audit.view. Every model call the school has made, and every suggestion the AI has put in front of somebody, searchable and exportable as CSV.

What is kept

Section titled “What is kept”

No prompt or response text is logged. Three tables back this page:

  • Calls — one row per model call, counts only: the feature, tier and model, token counts, cost, whether it succeeded and a short error kind, the duration, and who asked (a person, the system, or an API key).
  • Suggestions — what the AI proposed, a one- or two-sentence reason, the ids of the records it used, and what a person did with it (accepted, dismissed, or left alone). A proposed draft is kept here with real names restored, so this table can hold personal information.
  • Embeddings — computed from ticket, article and document text for finding similar records. No text, only ids, and each is re-read through the reader’s own permissions.

Why this page exists

Section titled “Why this page exists”

Every AI feature ships in a mode that shows its work — shadow keeps the answer, suggest asks somebody to accept or dismiss it — but a school still needs one place to see the whole pattern: which features are firing, how often the model is wrong often enough that somebody dismisses it, and what a technician did with what the AI proposed. That is this page, not a per-ticket history.

Section titled “Related”