Review activity

Open Home and follow its recent-activity link to Activity. Activity is a record of what happened in the selected organization; a computer’s detail panel separately shows its current state.

Find an event

Use the category and search filters to narrow the list. Open an event for its available context and follow linked resources, such as the affected computer or Blueprint, when you need to inspect their current state.

Useful questions include:

• Who changed a Blueprint, Policy, or App List?
• Which immutable version was prepared, released, or deployed?
• When was a computer adopted, reinstalled, or decommissioned?
• When did a deployment fail, resume, or roll back?
• Was a person invited or their role changed?

Check the selected organization and the relevant time before attributing an event to a support incident. An old failure in history does not, by itself, establish that the resource is still unhealthy.

Relate audit events to operations

For a computer problem, use its Diagnostics to inspect the exact command and retained evidence. For a deployment, use Deployment history to read the plan and outcome. The audit trail helps establish who requested the action and when.

During platform impersonation, audit attribution retains both the effective user and the originating administrator. The visible impersonation banner establishes the current session mode.

Export evidence

Use the export action to download the filtered activity as JSON. Confirm the filters before exporting and keep the file in your approved support/audit location. Event metadata can contain organization and device identifiers.

When asking for support, send the relevant time range and resource identities rather than an unexplained full history. Get support describes the evidence that makes an investigation easier.