Can I make Breeze AI ask before it changes anything?

It already does. Every action Breeze rates high risk (service restarts, patch installs, script runs, restores, Microsoft 365 and Google account changes and more) becomes an approval request and waits for a person instead of running.

Where do I approve AI actions in Breeze RMM?

In the chat where you asked, or on the Approvals page in the sidebar, which lists everything waiting for you across every client. The sidebar count and the notification bell tell you when something new arrives.

What is a four-eyes approval?

For the highest-impact actions, such as restores, Microsoft 365 account changes and remote sessions, the person who asked can't approve their own request. It goes to everyone with approval rights, and approving it needs a registered approver device. Denying never does.

What happens if nobody approves a request?

Every request has a timer. When it runs out, the request shows as Expired under Recent and the action never runs.

Is there a record of who approved what?

Yes. Every approval and denial is a row in the Audit Trail under the person who decided it, and the run of an approved action is logged as well.

How to Approve AI Actions Before They Run: the Approvals Queue

Name: How to Approve AI Actions Before They Run: the Approvals Queue | Breeze RMM
Uploaded: 2026-10-22
Duration: 3 min 24 s
Description: In Breeze RMM, every action the AI assistant rates high risk (restarting a service, queuing a patch, restoring a server) waits on the Approvals page until a person approves or denies it. Each decision lands in the audit log under that person's name.

In Breeze RMM, every action the AI assistant rates high risk (restarting a service, queuing a patch, restoring a server) waits on the Approvals page until a person approves or denies it. Each decision lands in the audit log under that person's name.

3:24 Captions: English Open on YouTube

What's in the demo

Approvals in the sidebar with a pending count, and the notification bell: "Approval requested" for a server restore a technician asked Breeze AI for
Clicking the notification lands on that exact request on the Approvals page: All organizations, sorted Expiring soonest, each card counting down ("Expires in 38 min")
Anatomy of a card: Acme Manufacturing, Restart service "Spooler" on ACME-WS-014, High risk, "Requested by Breeze AI · 5m ago · Expires in 24 min", and the impact line "Restarting "Spooler" will briefly interrupt it and anything that depends on it."
Approving a supervised request from my own chat: the Chrome patch for Acme's MacBook. Breeze re-checks permissions and the exact request before it runs
A four-eyes request (a server restore): the technician who asked can't approve it, and approving takes a registered approver device such as Touch ID, Windows Hello or the Breeze phone app
Deny with a reason, which never needs the device: toast "Action denied"
Recent, under the queue: the restore Rejected ("the approval was rejected, so it did not run"), the Chrome patch Completed, and "Kill process PID 4412 on ACME-WS-009" Expired from yesterday
Audit Trail: "Action intent rejected" and "Action intent approved" under Breeze Admin, and "Action intent executed" when the approved action ran

Questions this video answers

Can I make Breeze AI ask before it changes anything?: It already does. Every action Breeze rates high risk (service restarts, patch installs, script runs, restores, Microsoft 365 and Google account changes and more) becomes an approval request and waits for a person instead of running.
Where do I approve AI actions in Breeze RMM?: In the chat where you asked, or on the Approvals page in the sidebar, which lists everything waiting for you across every client. The sidebar count and the notification bell tell you when something new arrives.
What is a four-eyes approval?: For the highest-impact actions, such as restores, Microsoft 365 account changes and remote sessions, the person who asked can't approve their own request. It goes to everyone with approval rights, and approving it needs a registered approver device. Denying never does.
What happens if nobody approves a request?: Every request has a timer. When it runs out, the request shows as Expired under Recent and the action never runs.
Is there a record of who approved what?: Yes. Every approval and denial is a row in the Audit Trail under the person who decided it, and the run of an approved action is logged as well.

A note on the demo: the cards for the Chrome patch and the restore show internal tool names (remediate_vulnerability, restore_snapshot) as their headline. The narration describes each action in plain words. The notifications panel stays open over the Approvals page until about 1:29. All organizations, devices and people are fictional demo data, and no AI model was called during recording.

Do this on your own fleet

Everything in the video is in the product you get. Start the Cloud Beta in minutes, or self-host the open-source Community edition for free.

Start Cloud Beta Deploy for Free Book a Demo