Documentation

Approvals and permissions

Sanaf asks before anything it cannot undo, unless someone at your business has told it otherwise. Rules are set per kind of action, and per tool where you want finer control, so sending an email and updating a record are governed separately.

Last updated 2026-09-24.

Three answers, per kind of action

Every action Sanaf can take falls into a kind: read something, draft something, send something, change a record, spend money. For each kind you choose one of three answers: do it, ask me first, or never.

Setting the rule by kind rather than by app is the part that matters. "Never spend money" holds in every app you connect, including one you connect next month, which a per-app rule cannot promise.

It asks until you say otherwise

Out of the box, Sanaf asks before anything that leaves the workspace or changes something: sending, booking, updating a record, deleting. Work on its own desk, such as drafting a document or sharing a file it made, needs no ask.

You loosen it one kind of action at a time, from the approval card itself or from the tool settings of a connection. Spending money and setting up a new scheduled task are always asked about, whatever else you allow.

Attended and unattended

A request you typed and a schedule that fired at four in the morning are not the same risk. A rule can be limited to work somebody is watching, so a job may send follow-ups during the day and still hold them for you overnight, without you maintaining two jobs.

When it asks

An approval arrives where the work is happening: in the thread in Slack or Microsoft Teams, or in the console chat, and on a voice call Sanaf tells you the card is on screen. It says what it wants to do and why.

The card offers up to five answers: go ahead this once, yes for the rest of this conversation, always allow this, not this time, and never allow this. Some are left off for actions that must always be asked about.

If nobody answers, nothing happens. Work waits rather than proceeding on a timeout, which is the only safe default.

The record

Everything Sanaf did, everything it asked about, and everything it declined to touch is in the work log, with the rule that applied. That log is the answer to "what did it do today", and it is written to be read by someone who was not there.

Questions

Frequently asked

Can I make it never do something, permanently?
Yes. "Never" is one of the three answers, it is set per kind of action, and it holds across every app and every job, including apps you connect later.
What happens if nobody approves a request?
The work waits. Nothing proceeds on a timeout, and the pending item stays in the log until someone answers it or cancels it.
Does it ask every time, forever?
Only until you say otherwise. Choose "always allow this" on a card, or set the tool to always allowed, and it stops asking about that kind of action. Most teams start strict and loosen a kind at a time as they see what it actually does.