Audit reports

At a glance

Who uses it: Admins running periodic FERPA reviews and security teams investigating activity.
When to use it: Quarterly access reviews, after a parent complaint, during an annual compliance check.
Permissions required: School admin or district admin.
Navigation path: Administration → Audit log (raw log) and Reports → Audit (saved views).

Purpose

Audit reports turn the raw audit log into pre-built views designed for compliance work — access reviews, FERPA disclosures, sign-in anomaly checks — instead of free-form searching.

Built-in reports

Sign-in activity — successful and failed sign-ins by user, with IP and user agent.
Role changes — every grant or revoke of a role over a chosen window.
Record access — student record views and exports per user.
Exports — every FERPA dossier export with actor, target student, and timestamp.
Imports — every CSV import batch with row counts and outcomes.

Step-by-step

Run a saved report

Reports → Audit.
Pick a report (e.g. Record access — last 90 days).
Adjust the date range or actor filter if needed.
Click Run.

[SCREENSHOT: reports-audit-record-access] Reports → Audit, Record access report with a 90-day window and one user filtered.

Export

Click Export CSV from the report toolbar. Up to 10,000 rows per export — narrow your filter if needed.

Save your own view

From any report, apply filters.
Click Save view.
Give it a name. The view is visible to other admins at your school (or district, if you are a district admin).

Tips & best practices

Schedule a recurring Role changes review every quarter — this is the highest-signal audit for FERPA access.
Save a per-school Exports view that captures all FERPA dossier generations in the last 30 days.

FAQ

How long is the audit log retained? 7 years, independent of case retention.

Can I get audit data delivered automatically to my SIEM? Today: scheduled CSV email export. Real-time webhook push is on the roadmap — see Webhooks.