Skip to main content
Ari operates on an approval-first model: he never changes data or contacts a customer without a human clicking Approve. This page is the precise reference for what runs freely, what waits for you, and how to make the review step count.

​
The line, precisely

The rule of thumb: reading is free, writing waits. If an action would change a record in any connected system or put anything in front of a customer, it goes through approval.

​
One inbox for everything to review

Every item waiting on a human queues in your unified inbox: invoices ready to send, billing emails and support tickets to handle, contracts to approve for revenue recognition. It’s a single review surface across all your connected systems, so approvals never sit unnoticed in one tool while you’re working in another. You can act on any item from the inbox or from the Slack thread where the work started; they stay in sync.

​
How an approval works

1

Ari analyzes your request

You ask for an action (“send a payment reminder to Acme Corp”), and Ari works out what that requires across your connected systems.
2

Ari posts a plan, not a result

You get the full plan in Slack before anything happens: what will be done, who is affected, and the expected outcome. For an email, that means the actual recipient, subject, and body text.
3

You decide

Approve executes the plan as shown. Modify asks Ari to adjust it, which is faster than rejecting and re-asking because he keeps the context. Reject cancels; nothing happens.
4

Ari executes and confirms

On approval, Ari acts across your systems and posts a confirmation with the result in the same thread.
Approval is the point of no return. Once you click Approve, the action executes and cannot be undone from Slack. The plan is your review checkpoint; spend the ten seconds it deserves.

​
Review like a manager, not a rubber stamp

  1. Check who will be contacted and what will change
  2. Spot-check the numbers: is the balance right? the invoice ID?
  3. Ask: does this match what I asked for?
  4. Then approve
If anything is off, click Modify and tell Ari what to change. Take extra care on batch reminders, large refunds, and bulk record updates: read the full recipient list.

​
Extra guardrails on high-impact actions

For bulk operations, large refunds, and similar high-stakes requests, Ari asks additional verification questions before he’ll even present a plan. You can also raise the bar yourself with a standing instruction:

​
Automated tasks and approval

Tasks, Ari’s event-driven automations, run in one of two modes: Graduate automations slowly. Every new task starts in approval mode; watch a few runs and promote it to auto-execute only once the runs are boringly correct. Task chains execute end-to-end, so review the whole chain before enabling auto-execute on any step.

​
Every approval leaves a record

Who asked, who approved, what happened, and when: it’s all logged in the thread and in the LedgerUp platform’s audit history, which covers everything that runs through LedgerUp services. See Activity history.