Browse the knowledge centreKnowledge centreMake sense of your workspace.The complete manual 17 chapters · print or save
PRACTICAL GUIDEFree & Pro5 min read

Find who changed what

Answer one concrete question with a filtered activity record, its actor, affected object and recorded outcome.

For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.

On this page
By the end of this guide

Finish with an evidence reference and a precise description of the recorded change.

IN YOUR WORDPRESS WORKSPACE

Logged.ai → Activity → Events

01

Before you start

#

Available in Free and Pro. You need permission to view activity on the selected site, and the relevant activity must still be retained. Have an approximate date, action or affected account/object ready.

Free Activity: recent recorded changes. Actual Logged.ai Free 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.
Free Activity: recent recorded changes

Read the acting user, affected object and recorded result separately. Current content labels help navigation; they are separate from retained evidence.

Actual Logged.ai Free 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.Explore this screen in the demo
02

Find the relevant record

#
  1. Enter an action word in Find a type of change, such as role, plugin or content. Choose In this area if you know the category, then select Find changes.
  2. Open Refine by person, time or source. Use Affected user ID when you know whose account changed; use Acting user ID when you know who performed the operation. Add an object ID, outcome or execution channel only when it helps narrow the question.
    Where do I find a WordPress user ID?

    A user ID is a number, not a username or email address. If your account is already allowed to view and edit that user, open Users → All Users, find the account and choose Edit. Read the number after user_id= in the address bar: user-edit.php?user_id=42 means user ID 42. You do not need to save anything.

    Your own Profile page may have no user_id parameter. If the link is unavailable or you need your own ID, ask an authorized administrator to confirm the number. Use the ID from this WordPress installation; the same number on an unrelated installation can refer to someone else. On multisite, also confirm the selected site. Do not broaden permissions just to look up an ID.

  3. Choose a UTC date interval and select Apply filters. The start date is included; the end date is excluded.
  4. Open a relevant record. Read Actor, Affected object, Outcome and Captured field differences. If offered, follow Activity from this request to inspect linked records.
03

Example: who changed Maya’s role?

#

Fictional review

Start with role. If Maya is the affected account, enter Maya’s WordPress ID in Affected user ID—not Acting user ID. To cover 19 October 2026 in UTC, use From 2026-10-19 and Until 2026-10-20. Open the record and check who acted, which roles changed and the outcome. If the record names Alex as actor and Maya as affected user, do not describe Maya as having made the change.

04

Read the evidence carefully

#

The actor performed the observed operation; the subject is the account or object affected. Current profile labels help navigation but are not a historical profile snapshot. The recorded outcome distinguishes an attempt or failure from a stored change.

Missing before-and-after values do not establish that nothing changed. Unsupported operations, excluded categories and direct database edits can be absent. A shared request identifier adds context; it does not establish why the operation happened.

Search matches up to four terms against recorded action types, not private post content. Filters change the view and its exports; they do not change collection.

Open the content, then follow its history

For a retained supported post, page, product or order event, Open content, Open product or Open order opens its native WordPress/WooCommerce screen in a separate tab when your current permissions allow it. A current title helps you recognize the item; it is not a historical title snapshot. If the exact recorded revision still exists and is accessible, the revision link opens that revision. A deleted, restricted or unavailable item stays unavailable.

Use View activity in supported content and product lists or editors, and in legacy or HPOS order editors, to review that item’s retained events. The shortcuts in native lists and editors require current item access and permission to view Activity. Alongside an authorized Activity record, View item activity filters retained records for that item. Native order-list shortcuts are unchanged. The new tab preserves unsaved work in the editor.

Read recorded commerce changes

Supported price, stock and order changes show compact before-and-after values directly in Activity. These are the values retained with that event, including recorded currencies and any unset, unavailable or redacted side. They are not fetched from today’s product or order. Expand the event to inspect the supporting details; the display does not add evidence to stored records or exports.

Pro: once the filters answer your question, choose Save this Activity view to review them in a private saved-search form. Follow the saved-search guide before adding a schedule.

Recognize a change without retaining its private value

Activity includes clear markers for supported URL-slug, publication-date, comment and pingback-setting changes. Related date fields share one readable summary. These markers say that a field changed; they do not add its raw value or the article text to retained evidence. Untitled content still records a supported change when WordPress supplies its final URL slug.

Supported WooCommerce price, percentage and fractional-stock changes retain their available precision. Native scheduled-sale changes can record the effective price. This does not promise coverage of every commerce extension, custom data store or scheduler.

05

Check your answer

#
  • You can point to a specific event reference and its time.
  • You have kept the acting user and affected object separate.
  • Your explanation includes the recorded outcome and any missing evidence.

For a handover, export the relevant slice. With Pro, use a case when related evidence needs a retained decision.

06

If nothing matches

#
  1. Choose Reset, confirm the correct WordPress site, and start again with one action word.
  2. Widen the UTC interval and remove person/object filters one at a time. An affected account ID is not always the actor ID.
  3. Check collection, retention and System status. If the event predates collection or was removed, changing the search cannot bring it back. See collection and coverage limits.
ABOUT THIS REFERENCE

This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.

A question we haven’t answered?

Get help with your next step.

Contact support