Work through an investigation case
Review a case’s sequence, assign the next reviewer, and leave a clear decision supported by the retained evidence.
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
Another authorized investigator will be able to see what you reviewed, what remains uncertain and what needs to happen next.
Logged.ai → Cases & handover → Cases
This guide requires Pro and investigation access on the selected site. Start from an existing case. The public Pro demo supports reading and filtering but does not save notes, assignments or statuses.
Cases organize related observations and decisions. They are not a verdict about a person, and closing one does not undo a WordPress change or activate a response.

Filter by status, then open a case to inspect its retained evidence. Priority and associations guide a review; they do not prove intent or causality.
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- Open the Case list. Filter by Case status if useful, then open the case. Confirm its site, actor, assignee and displayed timezone.
- Read Follow the sequence. Inspect retained source evidence, the priority explanation and any request-evidence links. Read Investigation history before repeating work another reviewer completed.
- In Investigator WordPress ID, enter an authorized reviewer’s ID and choose Save assignee. Leave the field blank to unassign.
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=42means user ID 42. You do not need to save anything.Your own Profile page may have no
user_idparameter. 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. - Add an Investigation note describing the evidence, interpretation and next step, then choose Add note. Keep credentials and unnecessary personal data out.
- Choose the appropriate Status and select Save case status. To reopen a closed case, explicitly choose to reopen it as Open.
These are separate forms. Saving an assignee does not also save an unsent note or status choice. Reload after a successful change and confirm the retained history.

Inspect the connected source evidence before recording a conclusion. This fictional refund pattern is an operational review example, not proof of fraud or gateway completion.
Actual Logged.ai Pro 1.2.7, captured 9 November 2026 in the read-only demo. Fictional sample data dated 19 October 2026.Fictional note
“Reviewed the retained role-change event and nearby request evidence. The role change is recorded; the address-and-time association does not establish who made the request. Need the site owner to confirm whether the role change was expected. Next reviewer: check that confirmation before closing.” Adapt the note to actual evidence rather than copying it as a finding.
A shared local request identifier provides stronger context than an address-and-time association. Shared NAT, proxies and ordinary authorized activity are alternative explanations for an address link.
Priority helps order review. Neither a high priority nor a related sequence proves malicious intent, fraud or causality. Retained history records notes, assignment and status decisions; missing source evidence must stay explicit in the conclusion.
Open the exact supporting event
Use the event link in a case to open its retained Activity record in the correct site. Sign-in and current evidence permissions still apply. The link follows that event’s unique reference; another record that later reuses a numeric ID is not a replacement. Removed or expired evidence is shown as unavailable. A case note or link does not preserve the source forever or bypass retention.
- Confirm the site and remove any case-status filter.
- Open Incident rules from the Cases page and review the configured conditions.
- Open Cases & handover → Background processing to inspect the required saved configuration and explicit processing choice. Check the recorded worker state.
- Compare that state with the relevant retained activity. An empty case list can mean no admitted match, unavailable processing or missing evidence; it does not establish that the site is safe.
- The intended reviewer is saved, or the case is deliberately unassigned.
- Investigation history contains the note and status decision you intended.
- The note separates observed facts, uncertainty and the next action.
The case changed while I was reviewing it
Reload the current case, read the new history and reapply only the still-relevant change. A stale form should not overwrite another reviewer’s decision. See saving changes.
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.
Get help with your next step.