> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bizzclaw.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Approvals

> What Bizzclaw does straight away, and what waits for your yes.

Bizzclaw reads freely and acts carefully. Before it does anything that changes data, reaches another person or spends money, it shows you exactly what it's about to do and waits for you.

## How an approval works

1. Bizzclaw prepares the exact action, for example the email with recipient, subject and body.
2. It shows it to you and asks.
3. You say yes, and it runs exactly that action. If anything changes (a different recipient, a new time), it asks again.

An approval stays open for a limited time. If it expires, just ask again.

## Your request counts as consent

If you ask for something yourself, in your own message, Bizzclaw doesn't ask you a second time. "Move my 3pm with Dana to Thursday" moves the meeting.

This shortcut **does not apply** when:

* the work was started by a schedule, an event or an alert rather than by you;
* the request came from a shared Slack channel (only your direct messages count);
* Bizzclaw has read outside content (an email, a web page, a document) in the same task and is about to send something to someone else. It confirms with you first, so instructions hidden in that content can't act on your behalf.

## Always asks, every time

Some actions always need your explicit yes, even if you asked for them:

| Category | Examples |
| - | - |
| Spending money | Payments, purchases, budgets, top-ups |
| Deleting or cancelling | Deleting records, revoking access, cancelling meetings or subscriptions |
| Phone calls | Any outbound call on your behalf |
| Code changes | Merging, pushing or editing code, running workflows |

## What never needs approval

Reading: checking your calendar, searching your CRM, looking up an issue, reading a web page, recalling a past conversation. Bizzclaw does these straight away so it can give you a useful answer.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.