Catch regressions and fix at scale Pro
Activity log
Who changed what, and when: fixes, dismissals, reports, feedback, scans, manual tests, settings and more in one filterable log.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
The activity log is under Lumtera → Reports → Activity. Lumtera Pro adds an entry each time something happens: a fix is tracked, assigned, changed or verified; an alert goes out; a report is created, deleted or opened through a share link; the license or a setting changes; an issue is dismissed, restored or ignored site-wide; feedback arrives, is assigned or goes overdue; and evidence is recorded, such as a finished scan, a manual test result, a test session sign-off, a statement review, an applied fix or a burden assessment.
Each entry reads as a sentence, such as who assigned which issue on which page to whom. The table shows What happened, its Type, By and When, newest first, 50 to a page. Changes Lumtera makes on its own are credited to Lumtera (automatic), a scheduled task or WP-CLI, so you can tell a person's decision from an automatic one. Show picks All activity or one of 14 groups; By picks Anyone, one person or Automatic; From and To set a date range. Export CSV downloads exactly what the filters show.
Below the log, the Evidence ledger card shows the latest evidence entry and its hash, and Verify ledger checks that no earlier evidence entry was changed, removed or added. How long to keep activity has two settings: Keep entries for, 365 days by default, and Keep evidence for, which keeps evidence entries until you set a number of days.
Why does it matter?
Procurement questionnaires, audits and handovers all ask the same thing: what has been done about accessibility, and by whom. Without a record, the answer is a guess.
What do you get?
- One row per event, with the person (or scheduled task) behind it.
- Filter by person, type of event and date; export to CSV.
- Evidence entries are hash-chained, and Verify ledger shows whether any earlier one changed.
- Separate retention settings for activity (a year by default) and evidence (kept until you choose otherwise).
- Covered by WordPress's personal-data export and erase tools.
How does it work?
-
Work as usual
Lumtera Pro records its events as they happen.
-
Open Lumtera → Reports → Activity
Filter to the person, event or dates you need.
-
Export
Download the filtered log as CSV for an audit or a client.
Who is it for?
-
Procurement and audits
Show a buyer or an auditor a dated record of what was checked, fixed and dismissed, and by whom.
-
Handovers
A new team member or agency can read back through past decisions, including every site-wide ignore rule and its reason, before changing anything.
-
Accountability for settings
When checks, alerts, branding or scheduled checks are changed, the log says who changed which settings and when.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan. The screen, the CSV export and Verify ledger need an administrator and an active license.
- How long entries are kept
- Keep entries for: 365 days by default, up to 3,650, and 0 keeps everything. Keep evidence for: 0 by default, which keeps every evidence entry. Older entries are removed once a day, oldest first, and removing evidence is itself recorded.
- No secret values
- Settings changes name the settings that changed, not their values. License changes record the status and plan, never the key, and tracker tokens and webhook secrets are never logged.
- Personal data
- The log is included in WordPress's Export Personal Data and Erase Personal Data tools. Erasing replaces the person's name and keeps the entry. For evidence entries, a new ledger entry records the change, so Verify ledger still checks out.
- What it does not cover
- Everyday edits to post content are not logged; WordPress revisions keep that history. Fixes applied through Lumtera are logged.
Questions
Something else on your mind? Contact support
Who can see it?
Administrators.
Can entries be edited or deleted?
Not from the screen. Entries are removed only when they pass the retention period. Someone with database access could change them, which is why evidence entries are hash-chained and can be verified.
Can the same events go to other tools?
Yes. The log and webhooks share the same events, so anything recorded here can also be sent to Slack, Microsoft Teams or your own tools from Settings → Integrations.
More in “Catch regressions and fix at scale”
-
Pro
Email and Slack alerts
Hear about it when a publish adds new errors or feedback goes past its target, never twice for the same one, plus a Monday summary and a score history.
-
Pro
Compare scans
See what is new, what was fixed and what is still there between two scans, by check and by site part, with the likely cause marked.
-
Pro
Fixes queue: bulk fixes you review and approve
Propose the same fix on many pages at once — built-in fixes or text you write (and AI drafts, only if you connect an AI provider) — review every change, then apply and undo them in the background.
Activity log
Get it with Lumtera Pro
In every Pro plan. Personal is $75 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew