Invisible automation
Reading needs no permission. Anything that leaves the system needs a standing grant from you and one first confirmation. Money is never automated. What is not allowed waits in an approval queue.
Diagram as text
- An automation wants to take an action.
- Read-only actions (read mail, read calendar, read documents, fetch a web page) run without a grant.
- Actions that leave the system (send or reply to mail, label or archive mail, create or change a calendar event, create or edit a document, call an outside webhook) need a standing grant for that action type and a first-time confirmation.
- Money movements (transfer, purchase, refund) are refused and cannot be granted.
- With a grant that has been confirmed once, the action runs.
- Without one, it waits in the approval queue, and you approve or reject it. Approving also records the first-time confirmation, so the next action of that type runs unattended.
- Revoking a grant also clears the confirmation, so granting it again asks again.
What a grant is
You grant one action type at a time with a switch in Settings, Automation: send mail, reply to mail, label or archive mail, create or change a calendar event, create or edit a document, call an outside webhook. Grants are explicit and revocable, so nothing gains permission silently. Revoking one also clears its first confirmation, so granting it again asks again. The feature needs a paid plan.
Why the digest exists
“It ran while I was away” never means “I do not know what happened.”
Findings are collected and delivered once per period, as a plain list with the actions still waiting for you. Nothing pings per event, and a day with nothing to report sends nothing.