> 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.25/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://app.gitbook.com/s/LYHZWRVgpD7c9mHAx1Vk/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://run-ai-docs.nvidia.com/multi-tenant/2.25/organization-life-cycle/organization-offboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.