> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/multi-tenant/2.24/organization-life-cycle/organization-offboarding.md).

# Organization Offboarding

## Delete Tenants

Use this endpoint to remove a tenant from your NVIDIA Run:ai environment. You can choose between a soft delete (retains tenant data for future recovery) or a hard delete (permanently removes the tenant and all associated data). See [Tenant](https://run-ai-docs.nvidia.com/multi-tenant-api/2.24/organizations/tenant) API endpoint for more details.

Send a `DELETE` request to the `/api/v1/tenants/{tenantId}` endpoint:

* **Tenant ID** (required, *path parameter*) - The numeric identifier of the tenant you want to delete.
* **isHardDelete** (optional, query parameter):
  * Soft delete - `false` (default) - The tenant is marked as deleted but data remains in the system.
  * Hard delete - `true` - All tenant data is permanently removed.

**Example request:**

```bash
curl -X DELETE 'https://console.<DOMAIN>/api/v1/tenants/123?isHardDelete=true' \
  -H 'Authorization: Bearer <TOKEN>'
```

**Example response:**

```bash
{
  "uid": "string"
}
```


---

# 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://run-ai-docs.nvidia.com/multi-tenant/2.24/organization-life-cycle/organization-offboarding.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.