Skip to content

Approval modes

Updated View as Markdown

MazeGraph’s Ask, Auto, and Full modes control when a model-initiated chat write waits for your approval. They do not grant WordPress access or switch tools on. New sessions start in Ask mode, and each session keeps its own mode.

Compare the modes

Mode What happens when the assistant proposes a write
Ask Every model-initiated write waits for your approval of the proposed change. This is the default for new sessions.
Auto Only two operations are marked common: creating a draft and updating a draft. Other writes wait for approval.
Full A supported, undoable MazeGraph write may run without another prompt when the policy allows it.

The words “Auto” and “Full” describe the approval prompt only. They do not mean that the assistant can perform any action it chooses. Draft tools create or update draft and pending content; other write tools can move content to trash, update media text or terms, and change WooCommerce data. A published product update affects the live shop immediately, and a status change may send a WooCommerce email that cannot be unsent. A write without MazeGraph’s trusted undo support is not offered in chat.

Change a session’s mode

In the chat composer, open the permission mode menu beside the send controls and select Ask, Auto, or Full. You can set the mode before sending the first message or change it in an existing session. It applies to that session; it does not change other sessions or a site-wide setting.

If an approval card appears, read the change summary and the exact proposed input. Choose Approve only if the details match what you intended. Choose Refuse to stop the change; you can add a reason or tell the assistant what to do differently. Approval covers those exact arguments, so a changed proposal needs a new decision. It expires after the configured lifetime (15 minutes by default); a changed target, tool input, or policy invalidates it. MazeGraph rechecks policy and WordPress permissions before running the call.

MazeGraph records supported writes in the change history. See Review changes and undo for how to review a change and whether it can still be undone.

Safeguards that every mode keeps

Every proposed write still has to pass the site’s policy checks. The relevant tool must be enabled, the selected assistant must be allowed to use it, and WordPress must grant the signed-in person permission for that action. A policy rule can refuse the request or require approval regardless of the session mode. See Who may use tools for the access checks and How MazeGraph decides what may happen for their order.

If the conversation includes text read from the site—such as post content, comments, or plugin descriptions—MazeGraph treats that text as untrusted. A model-initiated write in that conversation still waits for approval in Auto and Full mode. The approval card warns you when site content is part of the request, so you can check the proposed change carefully.

These modes apply to model-initiated writes in chat. A change you make directly in a MazeGraph screen, such as saving your own Content Studio draft, is your explicit action rather than a model request. It still requires your WordPress permission and is recorded for undo. See Content Studio for its draft workflow.

Examples

Auto can skip a prompt for a common draft write

Suppose you ask the assistant to turn your own brief into a WordPress draft in a new session. If the draft tool is enabled, the assistant includes it, WordPress allows you to create that content type, and the proposed call is marked as common, Auto may run it without a separate approval. The result is still a draft, not a published post, and the change can be undone.

Full does not skip approval when site content is involved

Suppose the assistant reads an existing page and then proposes an update based on that page. Because the conversation now includes text from the site, MazeGraph asks you to review the proposed write even in Full mode. This gives you a chance to check that the page’s content has not steered the assistant into making an unintended change.

WooCommerce changes can affect a live shop

If an administrator enables the relevant WooCommerce write tool, a published product update changes the storefront immediately. An order status change can trigger configured notifications, and undoing it can trigger another notification. Full may skip the approval card only when policy allows; the person still needs the required WordPress permission, and the action is recorded with its undo conditions.

No mode can approve a denied action

If the draft tool is off, the selected assistant cannot use it, WordPress denies your permission, or a policy rule says deny, the action stops. Choosing Full cannot turn that refusal into approval. Check Availability and role access, the tool catalogue, and Policy Administration and Safeguards when an action is unavailable.

If a write is still waiting for approval

An approval prompt can appear in Auto or Full when site content is part of the conversation or an additional policy rule requires approval. Review the warning and the exact input in the card. If you do not recognize or want the change, refuse it; the assistant cannot treat refusal as approval or retry the same change unless you ask it to do something else.

If there is no approval card and the write is refused, the problem is likely a different check: a disabled tool, a WordPress capability, a policy denial, or a write that cannot be undone. Follow A tool is missing or refused and review Policy Administration and Safeguards.

Was this page helpful?

Your feedback helps us improve these docs.

Documentation

Type to search…

↑↓ navigate↵ selectEsc close