Approvals are how Sanaf checks with you before it does something in your business, such as sending an email, booking an appointment or changing a record.
The rule
Sanaf asks, unless a person said otherwise. Before it sends, books, buys or deletes anything, it stops and asks on a card where it is working. Nothing happens until somebody says yes.
A few things never need a card because they are Sanaf's own scratch work: handing you a file it made, and running code or writing files in its own workspace. When that code reaches one of your connected apps, the app's approval rule applies.
Where you answer
Sanaf asks in the same place you asked it for the work:
- Slack: a card in the thread.
- Microsoft Teams: a card with Approve and Not this time.
- Chat in the console: the request appears in the conversation.
Sanaf's overview in the console (select its name at the top of the left rail) also shows the waiting request, with Approve and Not this time. Either place decides it.
Your choices on a card
In Slack and in the console chat, a card can offer:
- Send it: approve this one action.
- Yes, for this chat: approve it, and let Sanaf do the same thing again in this conversation for the next four hours without asking.
- Always allow this: approve it, and stop asking about this tool of a connected app from now on.
- Not this time: decline this one action.
- Never allow this: decline it, and stop Sanaf from doing this again.
A choice made with Always allow this or Never allow this on an app's tool shows up on the Integrations screen next to that app's tools, where you can change it back.
Actions with no standing yes
Some actions ask by default, and their cards never offer Yes, for this chat or Always allow this: buying credits, setting up, changing or deleting a routine that runs on its own, refunds, deleting records and generating video. Buying credits and routines always go to a person, and no setting can change that.
Sanaf also asks when an action was suggested by something it read from outside, such as an email or a web page, and for everything before it is live.
Who can approve
Only an owner or an admin can decide an approval. In Slack or Teams, the person clicking must also have linked their account in the console: open Integrations and use Your Slack account or Your Microsoft account. Anyone else who clicks gets a private note saying so, and nothing is decided.
Changed your mind
In Slack, a decided card shows Undo for 10 minutes. If Sanaf has not acted yet, the action is cancelled. If it has, nothing can un-send it, but Sanaf is told to stop there and the card says so.
If nobody answers
A request waits for up to three days. If nobody answers, it expires and Sanaf does not do that work. How it is going in Settings counts how many went unanswered.
Change what it asks about
To set a rule for a single app tool ahead of time, open Integrations, open the app, and choose Always allow, Ask for confirmation or Never allow next to the tool.
If Sanaf keeps asking for something you do not want, tell it why, in the chat or on the Teach Sanaf screen.