Workspace / Requests
Local storage
Display detailReadable stories and guided controls.Changes what you see, not collection, alerts, response or permissions.

Explore Pro tools

LESS REBUILDING THE SAME REPORT

Set up the review once. Reuse it next time.

Save the filters for a client, store or team review, then schedule private reports from that saved search.

Scheduled reports in Logged.ai Pro, using fictional demo data.
Genuine plugin screen · fictional demo data · select to enlarge
Activate Pro

The Pro add-on is installed. Activate it in WordPress, then activate your licence for this site.

Included in Free

Filter the activity you need and export a private CSV or JSON record on demand.

Added by Pro

Reuse saved searches and generate private reports on a configured schedule, with optional report-ready notices.

Explore the stepsRead-only example · no site changes
1Save the scope

Choose the evidence and filters that answer your recurring question.

Save that definition so the next review starts from the same scope.
2Set the period

Choose the supported period and inspect the retained evidence it contains.

A structured local summary explains the selected records and their limits.
3Configure the repeat

Choose a daily or weekly schedule and, if needed, report-ready email notices. This example creates no schedule.

Background workers generate private reports. An authorized user still needs to open the report; a notice is not the report itself.

SELECT THE CHANGE AND THE DESTINATION

Get selected alerts where your team works.

Configure an email, Slack or HTTPS webhook destination and choose the supported activity that should trigger an alert.

Advanced alerts in Logged.ai Pro, using fictional demo data.
Genuine plugin screen · fictional demo data · select to enlarge
Activate Pro

The Pro add-on is installed. Activate it in WordPress, then activate your licence for this site.

Included in Free

Use the included critical security and failure notices. Routine activity notification emails are in Pro.

Added by Pro

Choose configurable rules and email, Slack or webhook destinations, then review recorded delivery results.

Explore the stepsRead-only example · no site changes
1Choose the change

Select a supported permissions-change event and review the rule conditions.

Start with a change your team needs to review; this example saves no rule.
2Choose the destination

Select an email recipient, Slack incoming webhook or HTTPS webhook you control.

Review the destination and its privacy terms before enabling it. This example makes no connection.
3Verify the result

After setup, check the recorded delivery result and confirm receipt with the intended recipient.

A destination accepting a message does not prove a person received or read it. Background processing must be available.

KEEP THE REVIEW TOGETHER

Pick up the review where you left it.

Keep related evidence, your notes and decisions in one case. Return to it yourself or let an authorized teammate continue.

Cases & handover in Logged.ai Pro, using fictional demo data.
Genuine plugin screen · fictional demo data · select to enlarge
Activate Pro

The Pro add-on is installed. Activate it in WordPress, then activate your licence for this site.

Included in Free

Find and inspect individual records, including the actor, result and captured differences.

Added by Pro

Review supported associations in one case, add notes, assign the review and retain its decision history.

Explore the stepsRead-only example · no site changes
1Plugin updated

A component update starts the review. Compare the recorded result with your planned maintenance.

A case keeps this record beside the related observations.
2Settings changed

A later configuration change adds context. Its sequence alone does not establish a cause.

Keep the source fact separate from your interpretation.
3Permissions changed

Review the captured role difference and whether the access change was intended.

Record a decision against the case and return to its history.
Also included: review priorities

Inspect an experimental local ranking, its contribution breakdown and evaluation coverage. This experimental ranking helps choose a review order. It is not an attack probability or a verdict.

Availability depends on supported sources and configuration.

Requests, in context.

Site 1 · Network 1 · Times shown in UTC

Review admitted request findings and the response recorded for each one. A finding does not establish intent or a successful attack.

Collection coverage and address privacy

WordPress layer only. Bounded configuration, source/diagnostic, traversal-shaped, compound query-shaped, component-metadata and method observations run at init, priority -999. Static files, cache hits, upstream responses and code that bypasses WordPress are not observed.

IP mode: masked. The default source is the direct peer. Forwarding is interpreted only through an explicitly configured trusted-proxy boundary. Source derivation and quality are shown with evidence. Exact-source policies require current full-mode evidence. A shared network address does not identify a person. Bodies, full queries, cookies and authorization headers are never retained. Query policies store only deliberately selected allowlisted numeric conditions.

Request retention: 7 days · Groups: 30 days

Cleanup and telemetry limits

Cleanup runs in batches of 500 per hourly WP-Cron run; delayed cron can leave a backlog. Last successful cleanup: not yet observed. Admission caps and policy expiry do not depend on cleanup.

Every retained row is an admitted observation, not a count of attackers or all traffic. The separate Logged.ai Pro add-on supplies server-log import. Retained imported findings remain readable here.

Request source and observer self-test

Filter requests

Leave a field empty for all values. Status accepts unknown, a class such as 4xx, or an exact code. Blocked by Logged requires a recorded local response; an external 403 alone does not qualify. Dates include the whole UTC day.

Source matching uses available retained context: a full address needs full privacy mode and sensitive-context permission; masks use IPv4 /24 or IPv6 /48. A shared address does not identify a person. This page always uses the current WordPress site.

Clear filters

Up to 500 matching observations, 100 group summaries and 100 policy-history entries. With filters, context is linked to the exported observations; group counts describe whole groups. Without filters, context includes recent site history. Each category declares its limit and whether more records exist.

Patterns over time

Groups combine admitted observations by this site, primary family, source label and UTC minute. They do not group people or exact IPs. Counts are admitted lower bounds, not all traffic; a request with several rule matches appears in one primary group. Samples may be unavailable after observation retention.

No retained groups are available.

Recent repeated-resource patterns

Current retained admitted findings only. Counts are lower bounds; missing telemetry is not quantifiable. Fixed UTC-minute boundaries can split a sequence. Site and exact-peer views overlap and must not be summed. No attacker identity, historical alert, exposure, prevention or automated-response eligibility is established.

Examined 0 of at most 500 current retained rows across five fixed one-minute windows. Row limit reached: no. Partial analyses excluded from thresholds: 0. Unknown final statuses: 0.

No qualifying pattern in this bounded retained view. This does not establish an absence of probing or missing requests.

Individual observations

No admitted matching observations are available in the selected retention interval. This can mean no matching traffic, unsupported routing, retention, sampling or capture failure.

Interpretation limits

These conservative rules do not provide complete attack coverage. Repeated-resource patterns use only the bounded retained view; arbitrary missing-path sequences are unavailable. The observer self-test checks a controlled WordPress request through the configured source boundary; it does not test all routing or prove the site is secure. Typed manual policies use a separate matcher revision; existing policies keep their original conditions.