rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Delete a Claude project

Last updated Automation Claude Enterprise

AI summary

Permanently delete Claude projects from your organization using the Delete Claude Project automation action; the project, its custom instructions, and knowledge documents are removed immediately with no recovery. You will need Create Automation or Edit Automation permission and an Anthropic Compliance Access Key with the delete:compliance_user_data scope; projects must have no attached chats. Templates are available to automate deletion with or without approval.

This automation action permanently deletes a Claude project from your Claude Enterprise organization. The project’s custom instructions and knowledge documents are deleted with it.

Before you begin

  • Your Rencore role includes the Create Automation or Edit Automation permission. Owner, Admin and Contributor have it. See Rencore roles.
  • Claude Enterprise is in Preview. It is available when your Subscription includes the Claude Enterprise connector.
  • An Anthropic Compliance Access Key with the delete:compliance_user_data scope, entered on the “Automations/Actions” tab of Manage consent. See Anthropic consent. Without it, the action fails with the message “The Compliance Access Key of the Claude Enterprise organization is not configured in the Automations/Actions consent area for this environment.”
  • A project with no chats attached. Anthropic does not delete a project while chats are still attached to it, so detach or delete those chats in Claude first.
  • Anthropic deletes the project immediately. There is no recycle bin and no recovery window.

Steps

  1. Open the automation in the Automation Builder. See Create a custom automation.
  2. Click + in the flow and select the Delete Claude Project action.
  3. In Project, check the Claude project to delete. It is prefilled from the inventory Claude Projects object.
  4. Click Save.
  5. Run the action on a single project you know is safe to remove first. Rencore Governance cannot test the delete scope without deleting content, so the first run of the action is also the first check of the key.

From an automation template

Two templates are available in the Automation template library. Both are run manually.

TemplateWhat it does
Delete Claude ProjectSends the project creator an email that the project is scheduled for deletion, then deletes the project. Use it when no further approval is needed.
Delete Claude Project (with Approval)Sends an approval request titled “Approve deletion of “project name"" to the project creator. If it is approved, the creator is emailed and the project is deleted. If it is rejected, the creator is emailed and nothing changes.
  1. Create an automation from either template. See Create an automation from a template.
  2. Trigger it manually for the project.

The policies Claude project is empty and Claude project not updated in 90 days recommend the Delete Claude Project (with Approval) template for the projects they find.

What you see

When the project is deleted, the run history shows “Claude project is successfully deleted” and the project is removed from the Claude Projects Inventory.

If it does not work

If the run fails, the run history shows “Claude project could not be deleted” with the reason from Anthropic. The most common reasons are:

  • Chats are still attached to the project.
  • Anthropic did not find the project. It may already have been deleted in Claude, and the Inventory updates on the next scan.
  • The automation key does not have the delete:compliance_user_data scope, or it was revoked.

Frequently asked questions

Can I recover a Claude project after the delete Claude project action runs?

No. Anthropic deletes the project immediately, and there is no recycle bin and no recovery window. The custom instructions and knowledge documents of the project are deleted with it.

Why does the delete Claude project action fail with a message about the compliance access key?

The Compliance Access Key of the Claude Enterprise organization is not entered on the Automations/Actions tab of Manage consent. The key needs the delete:compliance_user_data scope. Without it, the action fails.

Why does the delete Claude project action say the project could not be deleted?

The run history shows the reason from Anthropic. Common reasons are chats still attached to the project, a project Anthropic did not find because it may already be deleted, or a key without the delete:compliance_user_data scope or one that was revoked.

Which automation templates delete a Claude project, and how do they differ?

Delete Claude Project emails the project creator that the project is scheduled for deletion, then deletes it. Delete Claude Project (with Approval) asks the creator for approval first. If rejected, the creator is emailed and nothing changes. Both templates are run manually.

How can I check that my access key works before deleting Claude projects?

Run the action first on a single project you know is safe to remove. Rencore Governance cannot test the delete scope without deleting content, so the first run is also the first check of the key.