> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/identity-access-and-administration/resource-deletion-and-its-effects.md).

# Resource Deletion and Its Effects

Deleting a resource removes that resource from its supported use. Review dependent projects and retained data before deletion.

![Separate a source file from its knowledge base](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FWKNtrJiRqJhzzjj71vIX%2Fresource-deletion-and-its-effects.png?alt=media)

Operation examples only; no deletion was performed. Confirm the target IDs and affected workflows before sending a destructive request. Deleting a source does not establish that previously generated answers or external copies are removed.

<details>

<summary>Copy the example</summary>

```http
# Delete one resource from a knowledge base.
DELETE /v2/knowledge-bases/{knowledge_base_id}/resources/{resource_id}

# Delete the knowledge base itself.
DELETE /v2/knowledge-bases/{knowledge_base_id}

# These operations have different scopes.
# Check references and access before either operation.
```

</details>

## Before you begin

Permission to delete the resource and knowledge of its dependencies.

## Key concepts

| Term        | Definition                                                                                                                                                |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Archive     | Removal from active organization views through the supported archive operation. It differs from permanent deletion and from unpublishing.                 |
| Unpublish   | Withdraw the selected published availability of a project. Review active runs and trigger state separately.                                               |
| Revocation  | Withdrawal of a credential or access grant. Check dependent applications and separately issued links when access changes.                                 |
| Retention   | The period or policy for keeping a category of data. Deleting one resource is not a universal retention rule for all related systems.                     |
| Side effect | A change outside the returned answer, such as creating a record or sending email. Cancellation or release rollback does not undo a completed side effect. |

## Delete a resource

1. Identify projects, sources, or interfaces that reference the resource.
2. Use the resource’s delete control and read its confirmation.
3. Check dependent workflows and update references that are no longer valid.

The resource is removed and affected dependencies are identified.

## Behavior and limitations

Deleting a project or connection does not undo external provider writes. Archive, unpublish, disconnect, and delete have different effects. Do not assume deletion is a complete retention or erasure operation across all exported files, histories, and external systems. Use the relevant data-management controls for each resource.

## Related resources

[Organization Roles and Permissions](https://docs.stackai.com/technical-reference/identity-access-and-administration/organization-roles-and-permissions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/identity-access-and-administration/resource-deletion-and-its-effects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
