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

Make a useful review repeatable

Turn a useful review into a saved search, verify one private report, then add a schedule with a deliberate time period and recipient.

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

You will have a reusable search and know which evidence its reports include, when scheduled periods run and how long private copies remain.

IN YOUR WORDPRESS WORKSPACE

Logged.ai → Reports & exports → Saved searches and reports

01

Before you start

#

Requires Pro and investigation access on the selected site. Start with filters that already answer a real question. You must own the saved search to create its schedule; sharing a search does not grant other people evidence access.

Complete the local reporting-workspace check if offered. It does not email a report. Reports use their own encrypted database storage and prerequisites, separate from Free’s on-demand exports.

02

Save the view and verify one report

#
  1. Choose New saved search. Give it a useful title and select a report type: site activity, user activity, sensitive changes, authentication, WooCommerce or incident cases/local summary.
  2. Set only the necessary filters. User activity requires the actor’s WordPress ID. For incident reports, clear activity filters and use the case-status filter.
    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 Only me or Investigators on this site, then save. Keep credentials and personal information out of the title.
  4. Open the search and inspect its current results. Under Generate a report, choose the UTC period and CSV, JSON or HTML.
  5. Check the report’s generation state before downloading. Open the file and confirm it answers the intended question before setting up repeat delivery.

The requested period intersects the saved filters and current retention. A saved search with a fixed old date range will not automatically become a rolling review.

Start with the Activity filters you already chose

In Activity, choose Save this Activity view. Pro opens a separate tab at Save this Activity view, with supported filters copied into an unsaved, private form. Review those filters, enter a useful title, keep or change visibility deliberately, confirm the displayed site and choose Save search. Until you save, no search exists. Opening this form does not create a report, schedule or alert, and the original Activity page keeps its state.

The shortcut cannot carry the free-text Find a type of change query. Replace it with the appropriate Recorded action filter before using this shortcut. Review absolute UTC date bounds carefully: a saved old interval will stay fixed. In saved-search results, use the event link to inspect the exact retained evidence with your current permissions.

Pro saved searches: start with a useful review. Actual Logged.ai Pro 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.
Pro saved searches: start with a useful review

Two fictional saved searches illustrate reusable review scopes. Inspect each search’s filters before generating a report or creating a schedule; opening it does not send anything.

Actual Logged.ai Pro 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
03

Example: a weekly sensitive-change review

#

Fictional review

Create a search titled “Weekly sensitive changes” using the sensitive-changes report type. Leave absolute date bounds blank if you want each scheduled period to choose the time range. Generate one manual report for a known UTC interval and inspect it. Once its scope is right, add a weekly schedule at a chosen local hour in the team’s named timezone.

04

Schedule the review

#
  1. Open Schedules → New schedule and select your saved search.
  2. Choose daily or weekly cadence, local hour, named timezone and output format. Daily reports cover the previous local day; weekly reports run on Monday for the previous seven local days.
  3. Choose whether to enable the schedule and send a minimal summary to your current WordPress account email. Acknowledge the seven-day private report copies, then choose Save schedule.
  4. Inspect the saved schedule and recorded report-job state. WordPress cron depends on the site’s runner; the selected hour is not a guaranteed inbox delivery time.
Daylight-saving changes and late workers

A repeated clock hour creates one period; a skipped hour runs after the jump. Late workers consider at most seven intended delivery days. Check the named timezone and the recorded period instead of assuming a fixed UTC hour.

Pro schedules: check whether delivery is enabled. Actual Logged.ai Pro 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.
Pro schedules: check whether delivery is enabled

The example review is weekly at 09:00 UTC, with the schedule and email disabled. On your site, enable them deliberately only after verifying a manual report.

Actual Logged.ai Pro 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
05

Understand what is retained

#
  • A report contains bounded source membership, not a complete database snapshot. The limit is 10,000 records and 16 MiB.
  • Private report copies expire after seven days. Downloaded copies need their own appropriate retention handling.
  • Email contains a minimal summary and authenticated link, not a report attachment. Mail acceptance alone is not proof of receipt.
  • Removing a saved search also cancels its reports and removes its schedules. Review that consequence before deleting it.

Handle an unavailable report

A saved report’s manifest and job details must agree before its output is offered. A damaged or inconsistent report can remain visible with Records unavailable; an authorized owner can cancel it while healthy reports stay available. Cancellation does not recover missing evidence or recall a downloaded file. Generate a fresh appropriately scoped report from evidence still retained.

Pro report notifications make one mail attempt. A transport acceptance does not prove inbox delivery, and an uncertain notification is not automatically resent. Report lists are bounded views whose selected rows are rechecked; they are not a transactionally complete snapshot of the database.

06

Check the next run

#
  1. Confirm the saved search still returns the expected kind of evidence and the schedule is enabled if intended.
  2. Verify the recorded period, generation status and any email state separately.
  3. Open the generated report while it is available. For a notification, have the owner confirm receipt and access to the authenticated link.
The report is empty, delayed or unavailable

For an empty result, inspect the intersection of saved dates, report dates and retention. For delay, check the schedule, timezone and cron status. For an expired or inaccessible report, use current authorized evidence to generate another. See troubleshooting.

If Attempting remains visible: the delivery outcome is uncertain. Logged.ai does not automatically repeat that attempt, because a message may already have been accepted. Check the authorized destination and delivery diagnostics before deliberately creating another notification. A report remaining available does not prove its email reached an inbox.

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