> 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.md).

# Create & set up Tenant

Create a Tenant, attach the Data Plane and Compute, install Stacks, and make it ready for a team to deploy Data Products.

Complete after [Provision Data Plane](https://v2.dataos.info/operate/dataos-operator/provision-data-plane.md) has registered a healthy Data Plane.

{% hint style="info" %}
This page assumes a Tenant is the right boundary. If you have not made that call yet, see [Choosing between an Instance and a Tenant](https://v2.dataos.info/operate/dataos-operator/choosing-between-instance-and-tenant.md) for the decision flowchart and evaluation criteria.
{% endhint %}

## Steps

{% stepper %}
{% step %}

### Open Instance Admin

Open the DataOS home page.

Click the **Profile** icon.

Select **Instance Admin**.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-27980a2e2a6d3f72731ea9ca6aa791414eba3288%2Fannotely_image.png?alt=media" alt="Open Instance Admin from the profile menu"><figcaption><p>Open Instance Admin from the profile menu.</p></figcaption></figure>
{% endstep %}

{% step %}

### Create Tenant

Decide the [Tenant blueprint](https://v2.dataos.info/operate/dataos-operator/design-tenants.md) first, then work through this sequence.

In **Instance Admin**, click **Create New Tenant**.

Enter the Tenant title and description.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-cec261a03246b5a2ff4abb784ef63e737340035c%2Fimage%20(2).png?alt=media" alt="Enter tenant details and create the tenant"><figcaption><p>Enter the Tenant details and create the Tenant.</p></figcaption></figure>

Click **Create**.

{% hint style="info" %}
The Tenant status shows yellow while the Tenant is being created. The process takes up to 10 minutes.
{% endhint %}

{% hint style="warning" %}
Use stable naming. You can update titles and descriptions later, but frequent changes disrupt references and communication.
{% endhint %}

Repeat the steps to create more Tenants.

{% hint style="info" %}
Before creating a new Tenant, see [Tenants and blueprints](https://v2.dataos.info/operate/dataos-operator/design-tenants.md).
{% endhint %}
{% endstep %}

{% step %}

### Invite users and assign roles

Open the Tenant **Access** tab.

Click **+ Grant**.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-4abd824cbc531b1e60abdb21b92af43de9bf608b%2Fannotely_image%20(7).png?alt=media" alt=""><figcaption></figcaption></figure>

Choose the user and assign a Tenant role: **Tenant Admin**, **Data Developer**, **Data Consumer**, or **Data Admin**. See [Roles & Permissions](https://v2.dataos.info/operate/access-control/roles-and-permissions.md) for role details.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-740f995b819e8ad0279f78255798fd25a5b8b4c2%2Fannotely_image%20(8).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
First, grant **Tenant Admin** access to the users who manage the Tenant. Tenant Admins can then invite more users, assign roles such as **Developer** and **Consumer**, and manage Tenant resources, including Data Plane and Compute attachments.
{% endhint %}
{% endstep %}
{% endstepper %}

### Optional next steps

{% hint style="info" %}
**These steps are optional for you, not for the Tenant.** Connecting the Data Plane and attaching Compute are required before the Tenant can run any Data Product workload, but you do not have to be the one who does them. Once the Tenant exists and someone holds the **Tenant Admin** role, you can [hand off the Tenant](https://v2.dataos.info/operate/dataos-operator/create-tenants/hand-off-tenant.md) and let the Tenant Admin connect the Data Plane and [create Compute](https://v2.dataos.info/operate/tenant-admin/create-compute.md). Either sequence works: complete both steps here, or hand off and let the Tenant Admin complete them. Agree who owns them so they are not left undone.
{% endhint %}

{% stepper %}
{% step %}

### Connect dataplane

Open the Tenant **Settings**. Go to the **Dataplane** tab.

Click **+ Connect**.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-82c8e263a9478731a7d770a8359dac3979ffa7b0%2Fannotely_image%20(4).png?alt=media" alt=""><figcaption></figcaption></figure>

Select the Data Plane you provisioned earlier (see [Provision Data Plane](https://v2.dataos.info/operate/dataos-operator/provision-data-plane.md)).

Click **Create Connection**.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-f9f9e4f192ecf7455502f3bc4f39123d16fb1643%2FScreenshot%202026-05-29%20at%202.32.58%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The Data Plane must exist before you attach it to a Tenant.

The connection takes up to 10 minutes. The status stays gray during processing and turns green once connected.
{% endhint %}
{% endstep %}

{% step %}

### Attach Compute

In Instance Admin, go to the **Compute** section for the Tenant.

Click **+ Add**.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-9aeb1311be19111073e09eebfc634b6f2e2ee2cb%2Fannotely_image%20(5).png?alt=media" alt=""><figcaption></figcaption></figure>

Provide the node pool selector and related infrastructure details.

<figure><img src="https://3708017598-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjg0LlodDVRaNWLSqorQ%2Fuploads%2Fgit-blob-9a9d184e6f9b3b564fe8e0953b637d4f7956d814%2FScreenshot%202026-05-29%20at%202.48.53%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

Without Compute, the Tenant cannot run Data Product workloads.

{% hint style="info" %}
Compute creation takes 2 to 3 minutes. The status changes from **Pending** to **Active** when the Compute is ready.
{% endhint %}
{% endstep %}
{% endstepper %}

## Next steps

Configure the Tenant's resources, then hand it over:

* [Deploy Stacks](https://v2.dataos.info/operate/dataos-operator/create-tenants/deploy-stacks.md) the Tenant's Data Products need.
* [Hand off Tenant](https://v2.dataos.info/operate/dataos-operator/create-tenants/hand-off-tenant.md) to a Tenant Admin once the readiness checklist passes.


---

# 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.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.
