ActivityLog follows how your team uses its knowledge base: what gets read, what gets edited, who keeps it current, and how tickets move. Stale pages that people still depend on stand out.
Which of your pages people open, which tickets you moved, and what you wrote this sprint.
The Knowledge Base report filtered to Anne Dodsworth: the pages she edited this week, with the number of edits on each. Put it next to the team's most-read list to see whether her effort is going into the pages people rely on.
Anne's ticket activity for the sprint as a flow between states: the tickets she opened and moved, from the knowledge base's own ticket history.
The most-read pages, the authors behind them, ticket flow through the sprint, and the heavily used pages nobody has touched in months.
The pages people opened most this week, with the date each was last edited, from knowledge-base page views and edits. The top row is a runbook many people rely on that nobody has updated in over 60 days: the one to fix first.
The pages edited most this week, with the number of edits. Heavy editing on one page, here the onboarding page, usually means it is being rewritten. Read it next to the most-read list to see whether effort goes where readers are.
How tickets moved between states over the sprint, built from each ticket's status changes. A wide band stuck in one state is where work is waiting.
Knowledge use is read from your knowledge base's own activity: who wrote, who edited, who read and how tickets moved. SharePoint documents add the files that live outside it.
Pages and wiki entries created, edited and published, page views, tickets opened, moved and closed, comments and sprints, with the page title and author.
An ActivityLog package installed in your Umbraco site sends each change as it happens.
Documents viewed and edited, with the file name and site. Never the file content.
The read-only Microsoft 365 connection, approved once by your Microsoft 365 admin. It reads Microsoft's own audit trail.
Every page edit, page view, ticket move and comment is reported with who did it and when.
Authors and readers are matched to people by email. Pages and tickets keep the client or product they belong to in the knowledge base.
The most-read pages with their last edit date, the most-edited pages, top authors, ticket flow through the sprint and release tickets.
Authors see their pages being used. Leads spot the pages everyone reads and nobody maintains, and ask the owner to update them.
A page people keep reading but nobody has edited in a long time: over 60 days in our example. The most-read list shows each page's last edit date, so the gap is easy to see. Old is not always wrong; it is a prompt for the owner to check.
No. We record that a page was edited or read, by whom and when, with its title. The page content stays in your knowledge base.
The ready-made connection is for Umbraco. Another knowledge base or wiki can send its activity to the ActivityLog ingest API, with some setup on your side.
ActivityLog is in beta. Connect the tools you already use and get this report for your organisation.
See pricing →Questions first? Talk to us → · All use cases
