Approvals
Before an action that changes something outside the conversation (sending an email or a message, creating a calendar event, writing to a file, approving an invoice), your accomplice prepares it and shows an approval card: what exactly will happen, in plain words, with Approve and Deny. Nothing happens until you decide.
The card approves the exact action shown. If your accomplice wants to change a word of the email, it is a new card.
Three ways to decide
- Tap Approve or Deny on the card, in the conversation.
- From your phone. When no Mandala window is open, the card arrives as a notification. On the iPhone app, Approve and Deny are on the notification itself, after Face ID.
- In your own words. While a card is waiting, write "yes, send it", "go ahead with the Seafrigo one" or "no, not now". When your message clearly approves exactly that action, it decides the card.
Approval by words
An independent check reads your message and the waiting action and judges whether you clearly approved it; your accomplice never judges this itself. It needs the Jev risk check connected (Settings → Extensions → Jev risk check, with a TypeSafe key); without it, use the card.
Some actions always keep their card, whatever you write: payments, payables, payouts, refunds, transfers, deployments and deletions.
Questions from coding agents
When a coding session's agent asks permission for something, the question is an approval card too, answered from the chat, the Code page, a notification or your words. See Code.
After approval
The action runs and is followed until it settles (a Telegram message until Telegram confirms it, for example). It is recorded in Activity with the approval: who decided, when, and what exactly ran. If it fails, your accomplice tells you and does not retry silently.
Less asking
Approvals are the default for everything that matters. To let your accomplice do some things directly, see What your accomplice may do alone.