# Revoke or delete a connection

Revocation and deletion serve different purposes. Choose the operation based on whether you want to remove authorization while retaining the connection entry or permanently remove the connection and its associated managed resource setup.

| Action | Result | Typical reason |
| --- | --- | --- |
| Revoke | Clears the connection's stored credentials and marks access revoked. | Stop using a credential and reconnect later. |
| Delete | Permanently removes the connection and performs its resource teardown. | Retire a connection that should no longer exist. |

## Before you continue

Open **Workflows** from the connection to inspect its dependent automations. Decide whether to stop their schedules, select a different connection, or retire them. Removing access does not rewrite a workflow to use another service.

Check whether the resource is managed by Strive. Deleting a managed resource can have consequences for the stored files, tables, or vectors associated with it. Read the confirmation carefully. Deleting a connection to an external service should not be treated as a command to erase every item in that external account.

## Confirm and verify

Use the connection's revoke or delete action, review the named connection and workspace, and confirm only the intended operation. A revoked connection remains available for inspection but cannot keep using the wiped credential. Restore access through the applicable reconnection or credential flow.

A deleted connection disappears from the list. Creating another connection afterward is a new setup; it does not promise to restore the previous managed data or all references automatically.

## Data already produced

Records previously synchronized or produced by workflows have their own lifecycle. Revoking a connection does not by itself prove those records were erased. To remove source output records, use [Data source deletion](/docs/data/delete-source-records). To delete original provider files or tables, use their explicit data actions. These operations have different scopes and should be checked independently.