> 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/v1/tenant-readiness.md).

# Tenant readiness

Getting a Tenant ready is a **shared responsibility**. No single role does everything: the Operator provisions and hands over the Tenant, the Tenant Admin sets up access and data sources, and the Data Admin provisions the Lakehouse. This page is the end-to-end view: the steps that take a Tenant from "created" to "a team can build and run on it," and who owns each one.

Use it to coordinate a hand-off, to see where your part fits, or to check nothing is missing before a team starts work.

## Who does what

The steps run roughly in order, grouped by the role that performs them. Each links to the canonical how-to.

### Operator

The Operator does the setup that requires Instance-level authority, then invites a Tenant Admin and steps back to Instance-level [Manage access](/operate/v1/dataos-operator/governance.md) and [Monitoring](/operate/v1/dataos-operator/monitoring.md).

{% stepper %}
{% step %}
**Provision the Data Plane** in your cloud. See [Provision Data Plane](/operate/v1/dataos-operator/provision-data-plane.md).
{% endstep %}

{% step %}
**Create the Tenant** in Instance Admin. See [Create Tenant](/operate/v1/dataos-operator/design-tenants/create-tenants.md).
{% endstep %}

{% step %}
**Attach the Data Plane and at least one Compute.** See [Attach the Data Plane and Compute](/operate/v1/dataos-operator/design-tenants/create-tenants.md#2-attach-the-data-plane-and-compute).
{% endstep %}

{% step %}
**Create the mandatory Secrets.** See [Create mandatory Secrets](/operate/v1/dataos-operator/design-tenants/create-mandatory-secrets.md).
{% endstep %}

{% step %}
**Deploy the required Stacks**: Vulcan and the MCP Server. See [Deploy Stacks](/operate/v1/dataos-operator/design-tenants/deploy-stacks.md).
{% endstep %}

{% step %}
**Invite the Tenant Admin** and assign the role. See [Invite a tenant admin](/operate/v1/dataos-operator/design-tenants/create-tenants.md#invite-a-tenant-admin).
{% endstep %}
{% endstepper %}

### Tenant Admin

The Tenant Admin takes over the running Tenant, and these steps can begin as soon as the role is assigned. A Tenant is usable on day one once at least one data source and the required Stacks are ready.

{% stepper %}
{% step %}
**Register data source Secrets and Depots.** The Operator may seed the first data source during setup, but registering and governing data sources is the Tenant Admin's ongoing job. See [Add data sources and Secrets](/operate/v1/tenant-admin/add-data-sources-and-secrets.md).
{% endstep %}

{% step %}
**Invite the rest of the team and grant `Can Use`** on shared resources. See [Manage access](/operate/v1/tenant-admin/governance.md).
{% endstep %}
{% endstepper %}

### Data Admin

The Data Admin provisions and owns the Lakehouse (its namespaces, schemas, tables, and views) separately from the resources the Tenant Admin governs, and only when a team requires one.

{% stepper %}
{% step %}
**Provision the Lakehouse**, if the team needs one. See [Manage the Lakehouse](/operate/v1/data-admin/manage-lakehouse.md).
{% endstep %}
{% endstepper %}

For role definitions and the capability matrix behind these assignments, see [Roles & Permissions](/operate/v1/access-model.md).

## Readiness checklist

A Tenant is ready to hand to a team when:

* [ ] The Data Plane and at least one Compute are attached and active. *(Operator)*
* [ ] The mandatory state store Secrets are applied. *(Operator)*
* [ ] The required Stacks (Vulcan and the MCP Server) are deployed and healthy. *(Operator)*
* [ ] A Tenant Admin holds the role and can sign in. *(Operator → Tenant Admin)*
* [ ] At least one data source Secret and Depot are active. *(Tenant Admin)*
* [ ] The Lakehouse is provisioned, if the team needs one. *(Data Admin)*
* [ ] A sanity Data Product deploys and runs without errors. *(Tenant Admin / Developer)*

Once the Tenant is ready, a **Data Developer** builds the Data Product on Vulcan, together with the data-product-supporting resources it needs, such as Nilus. See the [Data Product Developer overview](/operate/v1/data-developer/data-product-developer.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 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://v2.dataos.info/operate/v1/tenant-readiness.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.