The Divi AI Agent can do real work on your site - and some of that work is hard to undo once it happens. Before it does anything in that category, it stops and asks you first. This article covers what that approval prompt looks like, the three risk levels behind it, and exactly which actions always ask.
What an Approval Looks Like
When the Agent reaches an action that needs your say-so, it posts an Approval Required message in the chat with the line "Approve or reject this action.", along with Approve and Reject buttons.
The Agent stops there. It does not move on to the next step, and it does not try the action again on its own - it waits for you to answer.
Clicking the Approve button, the message updates to read Approved, and then the Agent carries out that one action and picks back up with the rest of your request.
Clicking the Reject button updates the message to Rejected instead, and the Agent moves on without completing the action that triggered the approval.
The Three Risk Levels
Every action the AI Agent can take is tagged with one of three risk levels. You can see these tags yourself in the Agent's tools catalog, each with its own tooltip:
Risk level | Tooltip |
Safe | "Safe actions do not require confirmation" |
Moderate | "Moderate actions require confirmation when configured" |
Destructive | "Destructive actions require confirmation before execution" |
Most of what the Agent does is tagged Moderate, not Safe - adding a module, adjusting a design setting, writing text, and similar everyday edits are Moderate, and they still run immediately with no prompt, because Moderate only pauses when the individual tool's own definition calls for it.
A handful of Moderate actions do ask for approval, but most don't. Destructive actions always ask, with no exceptions.
What "When Configured" Means
The Moderate tooltip's wording - requires confirmation when configured - reads like something you can turn on or off; however, that's not possible.
Configured refers to how that specific action is built into Divi, not to any preference of yours. There is no toggle, setting, or option anywhere in Divi that changes which actions ask for approval, and no way to switch approvals off altogether.
Here's the actual rule: an action asks for your approval if it is tagged Destructive, or if that particular action was built to always ask regardless of its risk level.
A small number of Moderate actions fall into that second case, because each one creates something that sticks around and gets used elsewhere:
Creating a Theme Builder template
Creating a page
Assigning a module preset as the default for that module
Assigning an option group preset as the default for that group
Adding a rule
Every other Moderate action runs the moment you ask for it, the same as a Safe one.
Actions That Always Ask First
Because they're tagged Destructive, these actions ask for your approval every time, regardless of anything else. In everyday use, you'll most often meet them as:
Moving a page, post, or other item to Trash
Changing whether a page or post is published, drafted, or otherwise changed in status
Updating a page or post's title, slug, or written content directly, outside the Visual Builder
Applying a Divi layout to a page or post other than the one you have open in the builder, which replaces whatever Divi content is already there
Saving the page you're working on in the builder
Deleting a menu, removing items from a menu, or reordering items in a menu
Assigning a menu to a location on your site, or removing one
Deleting a Theme Builder template, updating an existing one, or assigning where one appears
Updating a Theme Option
Deleting a canvas or a workspace
Deleting an item from the Divi Library
Saving changes to Global Variables
Saving a module preset or an option group preset
Updating or deleting a rule or a command
Changing responsive breakpoint settings
If you don't recognize a term here, that's fine - the point of this list isn't to memorize it. It's to know that anything that trashes, deletes, publishes, saves, or otherwise locks in a change gets a pause and a prompt, no matter how you phrased your request.
Approvals and Sub-Agents
For larger requests, the Agent can split the work across sub-agents that run pieces of it at the same time. If one of those pieces hits an action that needs approval, the same Approval Required prompt appears in the chat. Approving it resumes just that piece of work, while the rest of the request keeps going.
If You Reject
Clicking Reject isn't just a stop button. The Agent treats it as an instruction: it skips that specific action, continues with the rest of your request, and adapts around the fact that it didn't happen. If you want it to know why - so it can adjust its approach instead of trying the same thing again - say so in the chat right after rejecting.
Staying in Control
A few other things work alongside approvals to keep you in charge of what happens to your site:
Ask mode exists for when you want to explore or get an explanation without any risk of a change - it can't do anything that would need an approval in the first place, because it can't change your site at all.
Restore to This Point is how you undo what the Agent already did. It isn't available while an action is sitting at an Approval Required prompt - answer that first, then restore if you still want to.
Nothing is permanent on the page until it's saved, and saving is itself a Destructive action that asks for your approval like everything else in that tier.
Between what always asks, what never does, and what you can undo afterward, you're never more than one click away from stopping something you didn't mean to start.