# Approvals: nothing changes until you say so

> TulipFarm proposes changes to your data and outside apps first. A change happens only after a person approves exactly what was shown.

Source: https://docs.tulipfarm.ai/concepts/approvals/

An approval is your decision to let a proposed change happen. When a chat or an agent wants to change your data or an outside app, it shows the change first and waits for you.

## How it works

1. A chat or an agent proposes a change, such as new rows or an email to send.
2. You review the exact change.
3. You approve it or reject it.
4. TulipFarm carries out only what you approved.

Three rules apply to every approval:

- An approval covers exactly what was shown. Nothing more.
- An approval grants no extra permissions.
- An approval request expires after 24 hours.

## Approved is not the same as done

An approved request is not a completed action. TulipFarm still has to carry out the change. Check the status to see if the change happened.

> **Caution:** Sometimes TulipFarm cannot tell if an action happened. This is an unconfirmed change. Do not repeat the action. Use its status or recovery action instead. See [Unconfirmed changes](https://docs.tulipfarm.ai/troubleshooting/unconfirmed-changes/).

## Where you see approvals

### In chat

When a chat wants to change data or an outside app, the request waits in the chat. For example, when chat creates a table, you review the exact fields and row changes in the chat before you approve.

### In My agent tasks

When an agent proposes row changes, you review them in **My agent tasks**.

| Item | What it is |
| --- | --- |
| **Proposed row changes** | The row changes that the agent wants to make. |
| **Review batch** | Opens the group of changes for review. |
| **Approve exact batch** | Approves exactly these changes. |
| **Reject batch** | Rejects the changes. |
| **Execute next approved change** | Carries out the next change you approved. |

Only you can approve a batch from your own task.

## Outside apps that ask first

Some actions in connected apps always ask first. Examples:

- Sending an email from Gmail
- Changes in Google Drive, Docs, Sheets, or Slides
- Creating or editing in Jira or Confluence
- Creating or moving cards in Trello
- Changes in your personal GitHub

## Agents never get extra access

An agent works with the permissions of the person who asked, narrowed by the agent's own limits. An approval does not add to these permissions.

## Related

- [Review agent tasks](https://docs.tulipfarm.ai/guides/review-agent-tasks/)
- [Approvals and agent permissions](https://docs.tulipfarm.ai/security/approvals-and-agent-permissions/)
- [Saved, activated, and running](https://docs.tulipfarm.ai/concepts/saved-activated-running/)
- [Integrations](https://docs.tulipfarm.ai/integrations/)