Workspace / Requests
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.

Request source

The connection peer is the default. Enable forwarding only when your server reliably supplies the configured header through the exact proxy boundary you control. This does not configure a server or discover a CDN.

Display timezone: UTC



Leave the proxy set empty for connection-peer mode. Forwarding is read only when the immediate peer matches this set. The chain is evaluated from the connection side; the first untrusted hop is the derived source. Earlier supplied entries cannot replace it. Maximum 16 supplied hops and 4096 bytes; malformed trusted-side input makes the exact source unavailable. Other forwarding headers are ignored.

The selected IP privacy mode applies before storage. A derived address is connection context, not a person. Changing this trust configuration immediately invalidates dependent exact-source targets; their physical cleanup is bounded and may need background retries. Path and query policies keep their own matching rules.

Observer self-test

This opens one harmless, authenticated URL on this site through the browser. A successful result establishes only that this routed request reached the normal plugin observer and its minimized synthetic evidence was admitted. It does not test static files, cache hits, CDN decisions or every path. Temporary policies still apply.

Current test
not run
Last successful observer test (display timezone)
Not recorded
Address derivation
Not recorded
Address quality
Not recorded