Approve the Assistant's actions
How the approval card works when the AI Assistant wants to publish or change something customers see, and how your unsaved edits in the checkout editor stay safe while it works.
The Assistant makes small, safe changes right away and asks for your approval before anything that customers would notice. After reading this page you will know what the approval card shows, what each result means, and what happens to edits you have not saved yet.
Approve or reject an action
Ask for the change
Ask the Assistant for something that needs approval, for example "Publish this checkout" or "Change the 59 PLN price to 49 PLN". Instead of doing it, the Assistant shows a card titled Action requires your approval. The card describes exactly what will happen, for example Publish the checkout "[name]" - customers will be able to purchase through it. Nothing has changed at this point.
Check the card
Read the description and make sure it names the right product, checkout or client. Some cards carry a Review or edit the draft link that opens the draft in its editor, so you can read or correct it before you decide.
Click Approve or Reject
Approve runs the action immediately. The card changes to Approved & executed and a line Approved and executed: [description]. appears in the chat. After publishing a checkout, the public checkout address is shown under that line as a link you can open or copy. Reject cancels the action; the chat shows Rejected: [description]. The action was not executed.
What the card can show
| Status on the card | Meaning |
|---|---|
| Approve / Reject | Waiting for your decision. Nothing has changed. |
| Approved & executed | You approved and the change is done. |
| Execution failed | You approved, but the change could not be made. The reason is shown, for example a missing payment gateway. |
| Rejected | You declined. Nothing changed. |
| Expired | The card is no longer valid. Ask the Assistant to prepare the action again. |
Typical failure reasons are written in plain words on the card: No payment gateway is connected. when you publish a paid checkout without one, The product is hidden or archived - publish it first., or The saved details of this action are no longer valid. Ask the assistant to prepare it again.
Publishing a page has one extra check: when the page still contains placeholder fields, the card explains that visitors would see them and offers Fill in the fields and Publish anyway.
Which actions need approval
Publishing, unpublishing and hiding (products, checkouts, lessons, modules, pages, automations), changing an existing price, canceling a client's subscription, retrying a failed payment, revoking access for many clients, sending an email to a client, and changing a running automation. The complete table is in What you can ask the Assistant to do.
Adding something new, such as a new price or a new draft lesson, does not need a card. For messages the Assistant posts or sends in your name, it shows the text and asks with quick-reply buttons instead.
Your unsaved edits stay yours
You can use the Assistant while a checkout is open in the editor (/checkouts/<id>) with changes you have not saved:
| Situation | What happens |
|---|---|
| The Assistant changes the checkout you are editing | The change appears in the editor by itself, without a reload. Your own edits stay in their fields. |
| You had unsaved edits at that moment | A notice says The assistant updated this checkout in the background. Your unsaved edits are kept - fields you edited keep your version when you save. |
| An approval card appears while you have unsaved edits | The card adds a warning: You have unsaved changes in the open editor. They will be kept, but consider saving them first so nothing conflicts with this action. |
| You click Save changes afterwards | Changes saved. Fields you edited keep your version; the Assistant's changes to other parts (for example prices) remain. |
| You leave the editor with unsaved edits | The Unsaved changes window offers Discard changes, Return to editing and Save changes. Save changes saves and then leaves. |
Good to know
If you and the Assistant change the same field, your version wins when you save. Save your own edits before asking for a larger change, so it is always clear which version is current. With everything saved, the Assistant says nothing about unsaved changes and no background notice appears.
Was this article helpful?