The activity log
Every consequential action in the console is recorded. The activity log is where you go to answer "who changed this?", "when was that published?", or "what did the handover cover?". For accountability and for picking up where a colleague left off.
What's recorded
Creations, publishes, resolutions, updates, assignments, and the like. Each as a plain-language line: who did what, to which thing, and when. Entries are written as readable sentences rather than raw database rows, so you don't need to decode them.
Finding what you need
- Filter
Narrow by date range, by the staff member who acted, by the kind of action (created, published, resolved…), or by the type of thing (a help request, an event, an announcement, a staff change…).
- Search and sort
Free-text search across entries, and sort by time, actor, action, or entity.
- Open a row for detail
Click any entry to see the full record behind it.
You can export the log as CSV from reporting when you need it outside the console.
Entries are cohort-scoped, with institution-level changes visible across cohorts. Who can see the full trail follows the roles model. The complete audit view is an admin surface.
Why it matters
A welfare product has to be able to show its work. The activity log is what makes the system accountable: it survives staff turnover, settles "what happened" questions without guesswork, and underpins the institution-facing evidence pack.
Troubleshooting
The log says it couldn't load, rather than showing entries
Deliberate honesty: a failed read shows "Couldn't load the audit log" with a Retry button instead of an empty table, because an empty audit page would read as "nothing happened here" when the truth is "the query failed". Retry usually clears it; the page also retries on its own after a failed first load.
It says the cohort does not belong to your institution
The cohort selected in the switcher is not one of your institution's, so the log refuses to filter by it and shows nothing rather than a partial list, because a partial audit log is worse than none. Pick one of your own cohorts from the switcher and the log returns.
Entries I expect are missing
Check the cohort first: content entries (events, blocks, to-dos) are scoped to the active cohort, so another cohort's changes live under that cohort in the switcher. Institution-level entries (links, help routes, staff changes) always show. If a date range is set, widen it; the range query caps at 1,000 rows and says so when it hits the cap.
Common questions
Can entries be edited or deleted?
No. The log is a record. That's the point: an audit trail you could quietly rewrite wouldn't be one.
Does it show student actions?
It records staff actions in the console for accountability. A student's own activity (like a help request) appears as the events it generates on the relevant ticket and in aggregate insights.
Next steps
Related
The fastest answer is usually one question away.