Flows and approvals
The steps your product goes through, written down as data rather than code: what happens, in which order, and where a gate stops for a person. Anything that spends money, publishes or deletes raises an approval request with the price on the button, and your yes is tied to that exact call, once.
A recreated panel in the style of the app: how a turn in this module goes, built only from what the module really does.
3 things you can do with it.
Steps as data
A process you can read and change, not code you have to maintain.
Gates
A step only runs when the one before it passed.
Approval requests
Spend, publish or delete stops and asks, with the price on the button.
Plain words in the one chat.
You never pick the module. Neo reads the request, picks Flows and approvals, and says why.
What you hold when it is done.
- A process that runs the same way every time
- Approval requests in one place
- A record of what was approved, and when
Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.