Feature
Human approval before the crew acts
Reads can proceed. Sending an email, sending a Telegram message, creating a calendar event, or deleting one waits for a person, because those actions leave the workspace or remove data.
When a step waits
A read never waits. A send, a delete, or another high-risk action waits even if the crew is marked autonomous. A plain write waits only when that crew’s autonomy is set to approval. Suggest-only crews may read and reason, and they may not change anything.
Example
The crew reads an unread Gmail thread and drafts a reply. The draft stays in Gmail and is not sent. The send step pauses. Someone on the workspace approves it, or the run stops there. The same pause applies to a public Zendesk reply and to a Telegram message.
What approval does not do
Approval is not a second model review, and it is not a legal sign-off. It is a pause in the run until a person lets that step continue. The run keeps the decision with the rest of the step history.
Questions
Can I let a crew send without asking?
External sends and destructive actions still wait, including when autonomy is autonomous. That includes Gmail send, Telegram send, Google Calendar create, and Google Calendar delete.
Does a draft send the email?
No. Gmail draft reply creates a draft. Nothing is sent until the send action runs, and that send waits for approval.