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

# Safety and approvals

> What a connected assistant asks before doing, what it can never do, and how to undo its changes

A connected assistant can change your workflows and agents, but it can't spend credits or act in your apps without your yes. Every change it makes can be undone.

## What needs your yes [#needs-approval](#needs-approval)

Before each of these, the assistant tells you what will happen and waits for you to agree:

* Running a workflow, an agent or a share page, or running one again. You see the estimated cost (and the inputs) first.
* Testing a workflow on sample data. You see the estimated cost first, and a test run is stopped if it costs more than the limit shown.
* Deploying a workflow. You see what will change in the live version.
* Turning on or changing a schedule, or resuming a paused one. You see when it will run and the cost per run.
* Publishing a share page, or changing what visitors see on one. You see the page copy first.
* Publishing or rolling back an MCP gateway, or changing a live gateway's API base URL. You see what goes live first.
* Trying an MCP gateway tool that can change data in your API (anything other than a read). You see the call first.

Cancelling a workflow run, pausing a schedule, switching off a share page or taking an MCP gateway offline happens straight away, because it stops things rather than starting them.

If an assistant asks you to approve something you didn't expect, say no. Nothing runs until you agree.

## What an assistant can never do [#never](#never)

A connected assistant can't:

* See your passwords, API keys, connected app tokens, or your MCP gateways' API credentials and client tokens. It gives you a dashboard link when you need to enter or create one.
* Change your approval settings, or always-allow an app action
* Add app actions that delete or permanently remove data in your apps
* Remove or move a workflow's Start or End step
* Work in a workspace you didn't choose when you connected it

Runs started by an assistant follow the same app approval settings as runs you start yourself. If a step or an agent needs a person to review an action, the run waits for that review.

## How do I undo a change? [#undo](#undo)

Before an assistant changes a workflow's steps, it saves the workflow as it was. After the change, it saves a new version. Both appear in the workflow's version history in the dashboard.

To undo a change, ask the assistant: "Undo that change." It restores the version from before the change. Restoring never deletes a version. It saves your current steps first, then adds the restored steps as a new version, so you can always go back again.

You can also restore a version yourself from the workflow editor. See [Publishing and Versioning](https://docs.fetchhive.com/workflows/publishing-and-versioning.md).

Restoring changes the workflow's draft only. Your deployed version stays the same until you deploy again.

For agents, the assistant tells you the old values when it changes something, so you can ask it to put them back.

## How do I stop an assistant? [#disconnect](#disconnect)

Disconnect it from **Settings** → **Security** → **Connected assistants**. See [Connect an AI assistant](https://docs.fetchhive.com/workspace/connect-assistants.md#manage-assistants).


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