> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/dataos-operator/create-tenants/hand-off-tenant.md).

# Hand off Tenant

Confirm the Tenant is ready, assign a Tenant Admin, and hand day-to-day operation over to them.

A configured Tenant is not finished until someone owns it. Handing off means confirming the Tenant can actually run workloads, assigning a Tenant Admin, and stepping back to Instance-level work.

## Confirm the Tenant is ready

Work through this checklist before you hand off. Each item is something a Data Developer will need on day one, and each one is faster to fix now than after a failed deploy.

* [ ] The **Data Plane** is connected and at least one **Compute** is attached and active.
* [ ] The required **Stacks** are installed and healthy. See [Deploy Stacks](https://v2.dataos.info/operate/dataos-operator/create-tenants/deploy-stacks.md).
* [ ] At least one **data source** Secret and its matching Depot are active.
* [ ] A **Lakehouse** is provisioned, if the team needs managed Iceberg storage.
* [ ] A sanity **Data Product** deploys and runs without errors.

{% hint style="info" %}
For the end-to-end sequence, including which role owns each step, see [Tenant readiness](https://v2.dataos.info/operate/tenant-readiness.md).
{% endhint %}

## Assign the Tenant Admin

Grant the **Tenant Admin** role to the person who will run the Tenant day to day.

1. Open the Tenant **Access** tab in **Instance Admin**.
2. Select **+ Grant**.
3. Find the user, or enter their email address to invite them directly.
4. Assign the **Tenant Admin** role.

The user receives an email to accept access. Once accepted, they hold the role and can begin.

{% hint style="info" %}
Grant **Tenant Admin** first, before other roles. The Tenant Admin can then invite the rest of the team and assign **Data Developer**, **Data Consumer**, and **Data Admin** roles themselves, without coming back to you for each request.
{% endhint %}

## Why delegate

In a small operating model you might administer Tenants directly. As the estate grows, delegation is what keeps it manageable. A Tenant Admin handles that Tenant's users, resources, and grants, while you retain central control of the Instance, Data Planes, and Tenant lifecycle. Instance authority never leaks into the Tenant, and Tenant authority never reaches the Instance.

## Point them at their first tasks

Send the new Tenant Admin to the [Tenant Admin overview](https://v2.dataos.info/operate/tenant-admin/tenant-admin.md). Their first tasks are usually to:

* Confirm the Tenant's [Compute](https://v2.dataos.info/operate/tenant-admin/create-compute.md) and [data sources](https://v2.dataos.info/operate/tenant-admin/add-data-sources-and-secrets.md).
* Invite the rest of the team and assign roles.
* Grant developers `Can Use` on the resources they need. See [Manage access](https://v2.dataos.info/operate/tenant-admin/governance.md).

From here, your scope returns to the Instance: [Manage access](https://v2.dataos.info/operate/dataos-operator/governance.md) and [Monitoring](https://v2.dataos.info/operate/dataos-operator/monitoring.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://v2.dataos.info/operate/dataos-operator/create-tenants/hand-off-tenant.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.
