> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tabs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tabs.com/_mcp/server.

# Approvals

> How Tempo asks before it changes anything.

Tempo reads freely and asks before it writes. Any change to your data or to a connected tool, like updating a record, sending an email, editing a spreadsheet, or posting to Slack, waits for your approval.

## Proposals

When Tempo wants to make a change, it shows a proposal card with exactly what it will do: which records, which values, and the full text of any message. Bulk changes are grouped into one proposal, and you can download the full list as a CSV.

On each proposal you can:

* **Approve** it. Click **Confirm**, or reply in chat, e.g. "yes, go ahead."
* **Edit** it. Tell Tempo what to change, e.g. "send it to [billing@acme.com](mailto:billing@acme.com) instead." An edited proposal needs a fresh approval.
* **Reject** it. Tempo doesn't run it and won't bring it back.

## After you approve

Tempo runs the change and reports what happened. Some changes start work that finishes later, like an ERP sync or an email send. Tempo shows the status of that work on the proposal so you can see when it's done or if it failed.

## Approvals on routines

Routines run while you're away, so they only ever propose. Their proposals wait on the routine until you review them. See [Routines](/tempo-routines).