Review findings with Take Action

Use Take Action to review AI findings assigned to you and start follow-up when an Automation is configured to handle them. This workflow uses Action Types in AI Settings and Raise an action in AI Studio Automations.

Understand a finding card

A finding is one issue or opportunity worth reviewing. In Recommended Moves, card includes:

• Headline: Actionable description such as "Recheck mapping rule for Software."

• Impact: Main number and unit, such as 61% confidence, down from 94%.

• Evidence: Short explanation with relevant data.

• Found by: Automation that detected finding, or Specialist when configured and actually responsible.

• Owner: Person or role responsible for review.

• Actions: Review/accept when handler exists, or Not now.

Cards show findings assigned to signed-in user, directly or through eligible role. Not now dismisses for that individual, not everyone in role.

Six finding shapes

The Action Type determines category and display defaults. Review deadline and potential impact when prioritizing findings.

Review and respond to a finding

1. Open Inbox and select assigned action. You can also open finding from Recommended Moves on a dashboard where Take Action is enabled.

2. Check headline, impact, reporting period, evidence, and the person or role responsible. Open linked analysis when available.

3. Select Act on this to accept finding and start a matching follow-up Automation. Select Not now if you do not want to proceed at this point.

4. Check resulting report, action, notification, or approval request. If an approval request appears, review evidence and choose Approve or Reject separately.

Act on this starts configured follow-up work. It does not approve an operational or financial change. When no matching follow-up Automation exists, ask administrator to check the An action is accepted trigger and activation.

How findings get there

Producing Automation runs on schedule or event, gathers data and uses Raise an action with configured Action Type. Action Type defines payload, evidence, impact, ownership and repeat-finding identity.

For example, weekly seat audit identifies unused licences:

1. Audit emits Opportunity for 34 dormant seats.

2. Assigned licence owner reviews estimated annual savings.

3. Accepting action triggers separate reclamation handler, if configured.

4. Handler can contact seat holders, wait for response and request approval before deprovisioning.

5. Next weekly audit rechecks usage. Same unresolved finding updates existing card when repeat-finding key matches.

A workflow must include required approvals and permitted integrations before making changes to external systems.

For administrators

To create findings, use Configure AI Action Types, then Raise an action from an Automation. Configure handler with When an action is accepted trigger and select matching Action Type where available.

Keep detection separate from handling. Several producers can raise same Action Type; handler can change independently. Place approvals before writes or irreversible operations.

Configure the acceptance-triggered Automation

Administrators must configure this separately from the Automation that first raises a card.

1. Open Admin > AI Studio > Orchestrate > Automations and create another Automation.

2. Choose On app event and select An action is accepted.

3. Under Which action types?, select Action Types handled by this Automation. If none are selected, the event applies to all accepted actions. Select specific types when intended scope is narrower.

4. Add investigation or follow-up steps. An additional Raise an action can create a second action card for a different decision. Configure its Action Type in AI Settings first.

5. Add Wait for approval before downstream steps that require human authorization. Save, test, and activate workflow.

6. Select Act on this for test card, then check Run History for follow-up Automation.

Example: AI cost spike card shows GitHub spend 22% above baseline. Recipient chooses Act on this; follow-up Automation prepares root-cause analysis and raises an approval request. Reviewer can approve or reject proposed notification after reading report.

If expected action does not appear

• No card: Check feature availability, producing Automation Run History, Action Type payload and default owner.

• Wrong recipient: Check Action Type Ownership and Automation's Owner override.

• Repeated cards: Check stable fields selected in Action Type Lifecycle.

• Cannot accept: Check whether matching handler Automation is configured and available.

• Unexpected action after acceptance: Review handler steps and approval gates.

Related content

• Configure AI Action Types

• Raise an action from an Automation

• Enable and configure AI Studio Copilots

• AI Studio - Automations