The AI assistant can look at your data freely, but before it changes anything, it stops and asks you first. This article explains what that means in practice, what makes it stop, and how to read the approval card before you click Approve.
What an approval gate looks like
When the assistant proposes a change, the chat pauses and an approval card slides in. The card has four parts:
Part | What it shows |
Summary | A one-sentence description of the proposed change. |
Affected rows | The count of rows the change would touch. |
Definition | The rule, filter, or change laid out the same way you'd see it if you built it by hand. |
Buttons | Approve, Edit, or Reject. |
Nothing happens until you click a button. Closing the drawer or clicking elsewhere does not approve it.
What makes it stop
The assistant stops and asks whenever a change would actually save to your organization's data — anything that sticks around after you leave the screen you're on:
Creating, editing, or deleting a rule (basic or advanced).
Adding or modifying a custom field.
Bulk-tagging cells.
Starting an export that sends your data somewhere outside Stateable.
Actions that only look at your data don't need approval — filtering the rows you're viewing, searching, summarizing rows, or pulling up a related help article all happen on the spot. The pause is only for changes that save something.
What to look at before approving
A quick checklist:
Row count. If you asked the assistant to tag "small group accounts" and the affected count is 11,402, but your data has more like 800 small-group rows — the assistant misread the question. Reject.
Field name. Make sure the field it's writing to is the one you meant. The assistant sometimes makes up a brand-new custom field (a column you add) instead of using an existing one; if so, tell it what you actually wanted in the chat.
Priority. If a new rule is being added with the same priority as an existing rule, you may want to bump one of them. The card shows the priority on the rule definition.
Editing before approving
Edit opens the rule in the normal rule editor. From there you can change which field it reads, change the tag value, or adjust the priority before saving. When you're done, you land back on the approval card with your version, ready to approve.
Reject is fine
Saying no isn't a failure — the assistant takes it as feedback and will often come back with a corrected version. A lot of conversations go ask → reject → "actually I meant…" → corrected ask → approve.
Safety for big changes
The bigger the change, the more careful the gate gets. A change touching under 50 rows usually shows a one-line summary; a change touching tens of thousands shows the row count in red and asks you to confirm twice.
Warning: The double-confirm is there to stop tagging from running away — for example, when a filter catches far more rows than you meant and would have tagged half your data.
Get help
Still need a hand? Start a conversation from the Support button in the app, or email [email protected]. We reply within one business day for most tickets.
Related articles
Last reviewed: 2026-05-27