> 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/dataos-operator/design-tenants/create-tenants.md).
# Create Tenant
Complete after [Provision Data Plane](/operate/v1/dataos-operator/provision-data-plane.md) has registered a healthy Data Plane.
## Steps
{% stepper %}
{% step %}
### Open Instance Admin
Open the DataOS home page.
Click the **Profile** icon.
Select **Instance Admin**.
Open Instance Admin from the profile menu.
{% endstep %}
{% step %}
### Create Tenant
Decide the [Tenant blueprint](/operate/v1/dataos-operator/design-tenants.md) first, then work through this sequence.
In **Instance Admin**, click **Create New Tenant**.
Enter the Tenant title and description.
Enter the Tenant details and create the Tenant.
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](/operate/v1/dataos-operator/design-tenants.md).
{% endhint %}
{% endstep %}
{% step %}
### Invite users and assign roles
Open the Tenant **Access** tab.
Click **+ Grant**.
Choose the user and assign a Tenant role: **Tenant Admin**, **Data Developer**, **Data Consumer**, or **Data Admin**. See [Roles & Permissions](/operate/v1/access-model.md) for role details.
{% 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 %}
{% hint style="info" %}
You can now hand off the Tenant for use.
A **Tenant Admin** can complete any remaining configuration.
{% endhint %}
### Optional next steps
{% stepper %}
{% step %}
### Connect dataplane
Open the Tenant **Settings**. Go to the **Dataplane** tab.
Click **+ Connect**.
Select the Data Plane you provisioned earlier (see [Provision Data Plane](/operate/v1/dataos-operator/provision-data-plane.md)).
Click **Create Connection**
{% 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**
Provide the node pool selector and related infrastructure details.
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 %}
## When to create a Tenant (not an Instance)
A Tenant is the right boundary for most requests: a proof of concept, a team or department use case, or any unit that can share Data Product operations and infrastructure. Choose a separate **Instance** only when the requirement needs a stronger boundary, strict infrastructure isolation, independent operations, an external or cross-organization boundary, or a separate compliance and lifecycle. In short: Tenant for shared operations and faster setup; separate Instance for hard isolation. This is a governance and operating-model decision, not just an infrastructure one.
{% 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 the new Tenant admin at the [Tenant Admin overview](/operate/v1/tenant-admin/tenant-admin.md). Their first tasks are usually to confirm the Tenant's Compute and data sources, invite the rest of the team, and grant developers `Can Use` on the resources they need. From here, you focus on [Manage access](/operate/v1/dataos-operator/governance.md) and [Monitoring](/operate/v1/dataos-operator/monitoring.md) at the Instance level.
---
# 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/dataos-operator/design-tenants/create-tenants.md?ask=&goal=
```
`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.