Review device-assistant findings
Find assistant work that needs a person, open the exact device conversation, inspect its evidence, and choose a separate response.
Before you start
- The organization must have device-assistant activity or a linked alert.
- The selected device and conversation must still be available under the current retention policy.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Open Activity and locate assistant work
Open Activity and review Needs a person, assistant-session counts, and recent rule or script outcomes. Use a linked alert or the notification bell when you already know the finding that needs review.
What you should see: You have a specific session and device, rather than an aggregate count.
Read the finding in its conversation
Open the linked device workspace and select the session. Read the original request, diagnostic calls, returned evidence, finding, confidence, and any explicit need for a person.
Check source freshness and missing evidence
Compare the session time with the latest device heartbeat and the relevant health, patch, software, or file view. If the evidence is stale or incomplete, request a new read-only check before acting.
Review the exact proposed action
If the assistant proposes a command, file operation, script, or other change, inspect its target, classification, and scope. Approve or decline only the displayed proposal; organization approval and device-user consent can be separate gates.
What you should see: The diagnostic conclusion and the change decision are recorded as separate events.
Verify the later device state
After any approved work returns, recheck the relevant device measurement and review Activity or device History. A successful command exit alone does not prove that the reported problem is resolved.
What you should see: The record contains the finding, decision, execution result, and a follow-up observation.
If something doesn’t work
The Activity count has no openable session.
Refresh Activity and confirm the selected organization. The underlying session may have aged out under retention or the device may no longer be accessible.
The finding is present but its evidence is stale.
Request a new read-only check in the device workspace and compare timestamps before approving a change.
The proposed action is waiting.
Review the conversation approval, organization command approval, device connectivity, and any separate device-user consent state.