Workspace / Response
PRO WORKSPACE 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
Open reports
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
Open advanced alerts
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
Open cases
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.

Automation, under your control.

Mode: Off

Automation starts off. Shadow mode observes eligible findings for at least 24 hours and creates no response policy. Activation needs a separate preview and confirmation.

Suppression email is not configured with both this rule and recipients. Suppression notices remain available locally in response history, Activity and System status.

Finalized findings examined
0
Eligible individual findings
0
Compound candidate evaluations
0
Findings on protected routes
0
Findings with unavailable route context
0

A complete finalized-finding scan has not been established; work may remain pending.

Exact source targeting is unavailable under the current privacy mode. Full address retention must be a separate, deliberate privacy setting.

The shared response switch is off. Automatic activation requires deliberately enabling it on the Free response screen.

REVIEW THE PREREQUISITE

Shadow mode also needs full address context.

This optional workflow requires explicitly retained full client addresses. You can keep your current privacy setting and leave automation off.

Review privacy options

Eligibility and coverage

Only a rolling minute with at least ten distinct eligible live findings, three reserved resource templates and both bundled configuration and source/diagnostic families can qualify. Custom rules, imported or synthetic evidence, ambiguous/partial findings and prior local denials do not qualify.

Every policy uses GET/HEAD, an exact currently retained source and a fixed expiry of at most one hour. Repeated attempts do not extend a policy. A new policy needs proof captured after the previous original expiry. Responses are local HTTP 429; they do not prove malicious intent, prevention or application effect.

Current native route support covers ordinary frontend requests. Native privileged sessions, recognized login and configured WooCommerce cart, checkout and account pages are protected. Unsupported administration, REST, AJAX, XML-RPC, custom business routes and action/token query contexts remain unavailable for automatic denial and continue through ordinary observation.

WordPress cannot see all static, cached or upstream requests. Collection limits and per-source truncation suppress new automatic policies. Source identities are not people; shared networks can contain unrelated users.

Suppression records are retained locally. Optional fixed suppression alerts use the separately configured Alerts recipients and cooldown; no recipients are enabled by starting automation.