# What stops for your approval > The actions Willo won't take without a yes from you, how an approval card works, and what Always allow covers and never covers. Last updated: October 16, 2026 Source: https://www.willo.ai/docs/chat/what-stops-for-approval Willo runs most work straight away, because it can be undone from **Business → Activity**. Actions that can't be undone, or that reach other people, stop first and show an **approval card** in the chat. Nothing happens until you answer. ## What stops Anything else runs without asking. **Email and accounts** - Sending an email campaign to your list (not a test copy to yourself). - Changing who is on your email list: setting the audience, importing a list, or removing or unsubscribing someone, and moving your email sending to your own account. Adding one address doesn't stop. - Creating member login accounts, and sending them password resets. - Deleting member accounts, each listed on the card. - Changing the address your site's login emails come from. **Payments** - Creating a Stripe product. - Renaming, re-describing, archiving or restoring a Stripe product. Archiving stops every sale of it. - Importing your existing Stripe products, from a card with a tick box per product. **Your database and backend** - Writing, changing or deleting rows, and dropping a table. Loading an attached CSV is the exception: Willo shows a dry run and asks in chat. - Removing or retyping a column, removing or rewriting an access rule, and adding or removing table triggers. Adding a column, or an ordinary access rule, doesn't stop. - Changing who can read or edit a table from your site. - Creating or replacing a database function. - Running SQL that you or your own AI wrote, shown word for word with any security findings. - Deleting a backend function, or running one. So does deploying one that runs with admin powers and no check on who calls it. - Scheduling a backend job, with its projected monthly cost. - Creating or changing a storage bucket. **Your site and business** - Deleting a file from the site. - Publishing, unpublishing or deleting a content item. - Setting or removing a redirect. - Pointing a custom domain at the site. - Publishing or discarding the draft, when you ask in chat. - Editing or deleting a business document. - Saving a new Agent Program, which charges its one-time build cost, and archiving one. - Saving to Memory in a turn where Willo read outside content, such as web pages. ## How a card works The card says what will happen, with the detail: statements, files, people, cost. Choose **Approve** or **Deny**; a deny can carry a reason for Willo. A card that holds several actions offers **Approve all** and **Deny all**. You don't have to answer at once: after a few minutes the work pauses and the card waits for up to **seven days**. Approving picks the work up where it stopped. After seven days the card expires and the action doesn't run; ask Willo again if you still want it. While a card waits, so does that request: a chat that seems stuck often has a card further up. If you send a new message instead, Willo first asks whether to skip the waiting action (**Send anyway**); work already done is kept. ## Always allow Many cards offer **Always allow**. It applies to that one kind of action, for the whole business, from then on: that action stops asking, for everyone on the business. To review or remove an Always allow grant, contact support from the **?** menu. Some actions never offer it, because a yes to the last one can't honestly cover the next: - Anything that puts mail in someone else's inbox: campaign sends, changes to your email list, creating member accounts and sending password resets. - Deleting member accounts. - Changing a Stripe product, and importing Stripe products. - Running SQL, creating a database function, changing who can read or edit a table, and destructive changes to access rules. - Publishing or discarding the draft, and setting or removing a redirect. - Saving an Agent Program. - Cards that hold several actions at once, or ask you to tick items. Running a backend function sits in between: Always allow covers ordinary calls, but some calls, such as ones that send email, still ask. An action that once ran on Always allow and now asks again is this rule, not a lost setting. ## Who can approve The person whose request raised the card, and any admin or the owner of the business. An editor can answer their own cards but not a teammate's. A viewer's chat is read-only, so a viewer never raises one. See [Roles](https://www.willo.ai/docs/team/roles). ## Agents and programs Cards raised by your own AI agent never offer Always allow, and one given in chat doesn't cover them. See [Approvals for AI agents](https://www.willo.ai/docs/ai-agents/approvals). Related: [How a turn runs](https://www.willo.ai/docs/chat/how-a-turn-runs), [Undo a change](https://www.willo.ai/docs/chat/undo-a-change).