Remote work

Using Fleet Runner with explicit targets

Bound remote operations to approved assets and preserve the audit trail.

Requirements

Your role must permit the operation and each target must belong to the active authorized workspace. Confirm the command or operation before dispatch.

  1. Select the intended registered targets.
  2. Review the operation scope and expected result.
  3. Submit the work once; watch queued, running and final states.
  4. Inspect per-target results and record any unresolved failure.

Cancellation and retries are lifecycle states, not proof that a remote change was undone. Do not include secrets in command text or evidence screenshots.

Before taking action

Confirm the active workspace, required permission, registered asset, and freshness of the data being used.

← Back to documentation