Administration

The activity log

Who did what, when, and from where — the record you reach for when something is off.

Written for School admin
On this page

This page has no sections.

Every action anybody takes at your school is recorded: who did it, when, from where, and to what. This is the screen you reach for when something is not as it was and nobody remembers changing it.

Who can do this

View Action Log. Admin holds it. It sits beside Roles & Permissions in the sidebar deliberately — both answer “who can do what here”, and this one is read when that answer turns out to have been wrong.

The Activity Log. Sensitive actions carry a shield marker — here, every school switch.

What a row tells you

Column
WhenDate and time
WhoThe person, by the name they had at the time
WhatThe action, in plain language — “Read notes about someone”, “Switched school”
RecordWhich object it touched
FromThe IP address the request came from
ChangesWhat actually changed — expandable, field by field

The name is frozen at the time of the action. Somebody who has since left the school, or changed their surname, still appears as they were. A trail that loses the name exactly when it matters most is not a trail.

Finding something

Four filters, above the table:

  • Search — by person, record or action.
  • Category — the same vocabulary as the permission catalogue: Attendance, Users, Academics, Finance, Settings. So the filter reads in the same language as the Roles screen.
  • Two more dropdowns for narrowing further.
  • A date range — From and To.

Sensitive actions

Some rows carry a small shield. Those are actions the system treats as sensitive regardless of who performed them:

  • Switching school.
  • Reading notes about someone.
  • Viewing a full profile, including its sensitive fields.
  • Role and permission changes.
  • Password resets.
  • Anything touching money.

The marker is there so a scan down a busy day surfaces those without filtering.

Reads are logged, not just writes

“Viewed a full profile” is a row. That is unusual and it is deliberate: on a system holding learner ID numbers, medical information and home addresses, knowing who looked matters as much as knowing who changed something.

Bulk actions read as one line

Importing 500 learners writes one row saying 500 learners were imported, not 500 rows. The individual objects hang off it as changes you can expand.

Without that, a single spreadsheet import would bury a whole day’s real activity.

Exporting

Export PDF produces the current filtered view as a document — the thing to attach to a governing-body report or hand to an auditor.

What it is good for

“Who changed this learner’s grade?” Filter by the learner, look at Changes.

“Why can this teacher suddenly see Finance?” Filter by category Users. Role changes are logged with what was granted.

“Was this account used from somewhere unexpected?” The From column carries the IP address, and Devices shows what is currently signed in.

“Did anyone actually see that announcement?” That is read receipts on the announcement, not this — see Announcements.

How long it is kept

Log entries are kept for a period that depends on how sensitive the action was — routine activity is pruned sooner than security-relevant events, oldest first. The things you are most likely to need later are the things kept longest.