Skip to content
Docs/Compliance, reporting & data/Review activity and system logs, and verify the chain

Review activity and system logs, and verify the chain

A tamper-evident, append-only record of who did what and every job the system ran — in plain English, with the technical detail one click away.

Staff portalWho: Managers and administratorsLast updated 3 September 2026
Flow

Why the chain can be verified

Entry 1 · hash(1)Entry 2 · hash(2)= f(entry 2, hash1)Entry 3 · hash(3)= f(entry 3, hash2)Verify chainintegrityVerified ✓ · nentriesBreak reported atthe altered entry

Diagram: Why the chain can be verified. Steps:

  • Entry 1 · hash(1)
  • Entry 2 · hash(2) = f(entry 2, hash 1)
  • Entry 3 · hash(3) = f(entry 3, hash 2)
  • Verify chain integrity
  • Verified ✓ · n entries
  • Break reported at the altered entry

Connections:

  • Entry 1 · hash(1) → Entry 2 · hash(2) = f(entry 2, hash 1)
  • Entry 2 · hash(2) = f(entry 2, hash 1) → Entry 3 · hash(3) = f(entry 3, hash 2)
  • Entry 3 · hash(3) = f(entry 3, hash 2) → Verify chain integrity
  • Verify chain integrity → Verified ✓ · n entries
  • Verify chain integrity → Break reported at the altered entry
Pallara does thisStaff actionStop / refused
Every entry carries a hash of the one before it. Change or remove one, and everything after it stops matching.
Walkthrough · 2 steps

Reading the log

Select a step to see the screen for it.

  1. 1Curated only shows plain-English entries; the quick filters and chips narrow by category, source, severity and date.
  2. 2Select an entry for the summary, actor, time, affected record and key facts — and the technical detail under its own disclosure.
Activity & System Logs.A log entry: Select an entry for the summary, actor, time, affected record and key facts — and the technical detail under its own disclosure.
Activity & System Logs.
1 / 2

Every change in Pallara is written to one log: staff actions, learner actions, automated jobs, integrations. Each entry is a plain-English sentence — *Pallara Showcase Admin posted grades for Applied Project* — with the identifiers, before/after values and hashes in a detail drawer rather than on the page.

  1. Open Compliance → More → Activity & System Logs. The Activity tab shows staff and automated changes for your provider.
  2. Choose Curated only for human-readable entries. All incl. raw writes adds every automatically captured row write — useful for an investigation, noisy for anything else.
  3. Use Search summaries…, the quick filters (Financial, Grades, Logins, Settings, AI), the source buttons, the category chips and From / To dates. The same date in both includes that whole New Zealand day.
  4. Select a row to open Log entry: summary, actor, time, the affected record and the key facts. Expand Technical detail for the redacted before/after values, the sequence number and the hashes.
  5. Select a request ID to see every entry produced by that one request; Clear request filter removes it.
  6. Load more fetches the next 50 older entries without losing your filters.
  7. Open System for cron, webhook, AI, scheduler, deploy, integrity and error events, with duration and detail per row.
Activity & System Logs with Curated only selected: plain-English entries, quick filters, and Verify chain integrity.
FIG. 1Activity & System Logs with Curated only selected: plain-English entries, quick filters, and Verify chain integrity.

Verify the chain

Select Verify chain integrity. Each entry carries a hash of the previous one; verification walks the whole chain and reports Verified ✓ with the number of entries checked, and writes a chain.verify event to the System log. If any entry had been altered or removed, the chain would break at that point and the page would say so.

NoteThe log is how an issue is traced in a minute rather than a fortnight: who changed the grade, when the invoice was issued, which job sent the email. Audit-readiness is a by-product.
Was this guide helpful?