WorkMonitor.

Help Center · Ai agents

Act on a finding

Acknowledge, dismiss, action, or dispute a finding an agent has raised, so it stops sitting open on the feed.

Who this is for

Owners, by default. Seeing the findings feed at all needs the same permission as opening Agents, and deciding a finding (Acknowledge, Dismiss, or Action) needs a stricter permission again; neither is in the default Manager role, so both are owner-only out of the box. Raising a Dispute on a finding has no permission requirement of its own, but you still need access to Agents to reach the finding you want to dispute.

Before you start

You're looking at a finding in the Findings section of Agents. Every finding shows its severity, its title and body, and, where the agent cited any, an Evidence list underneath.

Steps

  1. Open Agents and read the finding you want to act on, along with its cited evidence.
  2. To record a decision, select Acknowledge, Dismiss, or Action.
  3. To challenge a finding instead, select Dispute. A text field opens with the placeholder *"Why is this finding wrong or unfair? A person is required to review it."* Type your reason, then select Raise dispute (or Cancel to back out without sending anything).

What happens next

Selecting Acknowledge, Dismiss, or Action updates the finding's status right away. A toast confirms it (for example, "Finding acknowledged"), and the finding is labelled with its new status on the feed. Raising a dispute shows a toast, "Dispute raised" (*"A human will review it."*), and clears the form.

If it doesn't work

  • If you can't reach Agents at all, you'll see "Agents are unavailable": *"You don't have access to this workspace's agents."*
  • If deciding a finding fails, you'll see a toast: "Couldn't update the finding".
  • If raising a dispute fails, you'll see a toast: "Couldn't raise the dispute".
  • Raise dispute stays disabled until you've typed a reason.

Related

  • The agent crew (overview)

More in Ai agents

Still stuck?

Every article here is checked against the code it describes. If this one does not match what you are seeing, that is a bug in the article and we want to know.