> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/mutations/deletetenant.md).

# deleteTenant

Manually delete a tenant by setting deleted\_at via soft-delete.

Audience: Programmer

Manually delete a tenant by setting deleted\_at via soft-delete. This triggers the soft-delete half of the tenant lifecycle — the row remains in the database and can be reactivated via restoreTenant during the grace period. Nothing hard-deletes the row, so the tenant keeps its name for good.

The target tenant is named by input.tenantId. The caller must hold ROLE\_ADMIN on it; ROLE\_SYSTEM satisfies this for system flows. A tenant in any registration status can be deleted; a registration that is still running (status pending) notices the delete itself and deactivates the organization it created. No other registration can take the tenant's name.

**Served by:** [management](https://docs.pyck.cloud/graphql-api/services/management.md)

## Arguments

| Name    | Type                                                                                  | Default | Description |
| ------- | ------------------------------------------------------------------------------------- | ------- | ----------- |
| `input` | [DeleteTenantInput](https://docs.pyck.cloud/graphql-api/inputs/deletetenantinput.md)! |         |             |

## Returns

[DeleteTenantResponse](https://docs.pyck.cloud/graphql-api/types/deletetenantresponse.md)!

## Example

Manually triggers the soft-delete half of the tenant lifecycle by setting deleted\_at. The tenant-lifecycle NATS subscriber observes the resulting CRUD event and starts DisableTenantWorkflow to deactivate the Zitadel org. A registration that is still running notices the delete itself. Returns an error when the tenant does not exist; idempotent on already-deleted tenants. The tenant row stays in the database and can be reactivated via restoreTenant during the grace period. The caller must hold ROLE\_ADMIN on input.tenantId.

```graphql
mutation DeleteTenant($input: DeleteTenantInput!) {
  deleteTenant(input: $input) {
    success
  }
}
```

**Variables**

```json
{
  "input": {
    "tenantId": "<tenant ID>"
  }
}
```


---

# 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.pyck.cloud/graphql-api/mutations/deletetenant.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.
