> ## Content Index
> Fetch the complete content index at: https://blog.cloud-station.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Agents cannot delete unless you allow it
- URL: https://blog.cloud-station.io/changelog/agents-cannot-delete-unless-you-allow-it/
- Published: 2026-09-24T09:00:00.000Z
- Updated: 2026-09-24T17:07:15.000Z
- Description: Every connection and every saved API key now refuses deletes by default. Reading, updating and creating keep working, and you decide per key and per connection what agents may do.
- Author: Oumnya Benhassou
- Tags: #changelog, #cat-security, #tr-agents-cannot-delete-unless-you-allow-it

An agent working on your behalf holds real access: your SharePoint, your Google Drive, your Gmail, the API keys you saved for it. Until now that access had no opinion about what the agent did with it. An agent that decided to “test” a delete could delete.

From this release, deletes are refused unless you allow them. This applies to every connection and every saved API key, on every task, without you changing anything. Reading, updating and creating work exactly as before.

![The Permissions dialog for a Google Drive connection with Read, Update, Create and Delete switches](https://blog.cloud-station.io/content/images/2026/09/cl191-permissions-dialog.png)

Each connection has four switches. Read is always on. Delete is off until you turn it on.

## What you can do now

- Open Settings, then API keys or Connections, and see at a glance what each key or connection lets agents do: Read, Update, Create, Delete.
- Turn Delete on for a specific key or connection when you want agents to remove content there. You are asked to confirm, and you can turn it off again at any time.
- Rely on the same rule across SharePoint, OneDrive, Outlook, Teams, Planner, Power BI, Power Automate, Business Central, Google Drive, Gmail and Google Calendar, and across every API key used through the platform.
- Find every blocked attempt in the audit log, with the agent and the conversation it came from.

![Confirmation dialog asking whether to allow agents to delete with this connection](https://blog.cloud-station.io/content/images/2026/09/cl191-delete-confirm.png)

Turning Delete on asks first, because most services cannot undo a delete.

## Why it matters

Deleting is the one action you cannot take back. A video removed from a channel, a file gone from a shared drive, a customer record dropped from an ERP: none of these come back with another command. Everything else an agent does can be corrected.

So the default is now the safe one. An agent can look things up, change what exists and add new items, which covers almost every job. Removal is a decision you make, per key or per connection, not something an agent gets for free with the credential.

The rule also catches deletes that hide behind other verbs. Many services delete through a regular request to a path such as `chat.delete`; those are treated as deletes too.

![The Connections settings page showing each connection with its Read, Update, Create and Delete chips](https://blog.cloud-station.io/content/images/2026/09/cl191-settings-connections.png)

Connections show their permissions on the card. A struck-through Delete means agents cannot remove anything there.

## Example workflows

- **Agencies:** an agent publishes and edits client content on Drive and YouTube all day, and can never remove a client’s file or video by mistake.
- **Finance and operations:** an agent creates and updates invoices in Business Central; cancelling or deleting stays with the people who own the ledger.
- **Internal IT:** turn Delete on for one connection during a cleanup job, then turn it off again when the job is done.

## What’s next

When a delete is blocked mid-task, you will not have to go to Settings to unblock it. The next entry covers the card that appears in the chat and lets you allow that one call, or deletes for a short while, in one click.